奇怪的堆栈在android崩溃报告 [英] Strange stack at android crash report
问题描述
$ b (MainActivity.java)
at __null __。access $ 102(MainActivity.java)
at __null __。access $ 200(MainActivity.java)$ _ $ _ $ _ $ _ $ _ $> )$ _ $ _ at __null __。access $ 500(MainActivity.java)
at ru.yandex.subbota_job.multiplicationtable.MainActivity.onEnterPressed(MainActivity.java)
at ru.yandex.subbota_job.multiplicationtable.KeyboardFragment .onClick(KeyboardFragment.java)
at android.view.View.performClick(View.java:4463)
at android.view.View $ PerformClick.run(View.java:18789)
android.os.Handler.handleCallback(Handler.java:808)
at android.os.Handler.dispatchMessage(Handler.java:103)
at android.os.Looper.loop(Looper。 java:193)
at android.app.ActivityThread.main(ActivityThread.java:5299)
at java.lang.reflect.Method.invokeNative(Method.java)
at java .lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit $ MethodAndArgsCaller.run(ZygoteInit.java:829)
at com.android.internal .os.ZygoteInit.main(ZygoteInit.java:645)
at dalvik.system.NativeStart.main(NativeStart.java)
我不明白访问$ xxx函数是什么?
此外,formatElapsedTime不是直接或间接地从onEnterPressed调用的!那绝对是! formatElapsedTime是通过runOnUiThread从定时器线程调用的。这是非常罕见的错误已经发生在第二次只有在两个不同的设备。
请帮助,任何想法!
我有很多 __ null __
。
这是Firebase堆栈跟踪反混淆器无法明确确定堆栈跟踪中混淆堆栈框架的几种方法中的哪一个的原始方法。这不应该发生在未来的崩溃。
I receive some crash reports from android (with java.lang.NullPointerException), but I don't understand what mean __null __ in stacktrace below:
at __null__.formatElapsedTime(MainActivity.java)
at __null__.access$102(MainActivity.java)
at __null__.access$200(MainActivity.java)
at __null__.access$500(MainActivity.java)
at ru.yandex.subbota_job.multiplicationtable.MainActivity.onEnterPressed(MainActivity.java)
at ru.yandex.subbota_job.multiplicationtable.KeyboardFragment.onClick(KeyboardFragment.java)
at android.view.View.performClick(View.java:4463)
at android.view.View$PerformClick.run(View.java:18789)
at android.os.Handler.handleCallback(Handler.java:808)
at android.os.Handler.dispatchMessage(Handler.java:103)
at android.os.Looper.loop(Looper.java:193)
at android.app.ActivityThread.main(ActivityThread.java:5299)
at java.lang.reflect.Method.invokeNative(Method.java)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:829)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:645)
at dalvik.system.NativeStart.main(NativeStart.java)
And I don't understand what access$xxx functions is?
Furthermore, formatElapsedTime is not called from onEnterPressed neither directly nor indirectly! That is absolutely! formatElapsedTime is called from timer thread through runOnUiThread. This is very rare bug has occurred for the second time only on two different devices.
Help, please, by any idea! I have a lot of __null__
.
This was the old behavior when the Firebase stack trace deobfuscator was unable to unambiguously determine which of several methods was the original method for an obfuscated stack frame in a stack trace. This should not happen for future crashes.
这篇关于奇怪的堆栈在android崩溃报告的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!