Android emulator 有人懂这个的语法吗?

Android emulator 有人懂这个的语法吗?,android-emulator,Android Emulator,我知道这是我第二次发布错误消息,但请耐心等待,因为我最终会完全理解如何破译这些日志。但是有人能帮我理解为什么我的日志开始出现错误,然后开始说我的仿真开始工作了吗?您的问题与仿真程序开始运行这一事实无关,您的问题是这一行: 05-18 03:36:42.250: E/Trace(3525): error opening trace file: No such file or directory (2) 05-18 03:36:42.640: D/AndroidRuntime(352

我知道这是我第二次发布错误消息,但请耐心等待,因为我最终会完全理解如何破译这些日志。但是有人能帮我理解为什么我的日志开始出现错误,然后开始说我的仿真开始工作了吗?

您的问题与仿真程序开始运行这一事实无关,您的问题是这一行:

    05-18 03:36:42.250: E/Trace(3525): error opening trace file: No such file or directory (2)
    05-18 03:36:42.640: D/AndroidRuntime(3525): Shutting down VM
    05-18 03:36:42.640: W/dalvikvm(3525): threadid=1: thread exiting with uncaught exception (group=0x40a71930)
    05-18 03:36:42.732: E/AndroidRuntime(3525): FATAL EXCEPTION: main
    05-18 03:36:42.732: E/AndroidRuntime(3525): java.lang.RuntimeException: Unable to instantiate application android.app.Application: java.lang.NullPointerException
    05-18 03:36:42.732: E/AndroidRuntime(3525):     at android.app.LoadedApk.makeApplication(LoadedApk.java:504)
    05-18 03:36:42.732: E/AndroidRuntime(3525):     at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4364)
    05-18 03:36:42.732: E/AndroidRuntime(3525):     at android.app.ActivityThread.access$1300(ActivityThread.java:141)
    05-18 03:36:42.732: E/AndroidRuntime(3525):     at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1294)
    05-18 03:36:42.732: E/AndroidRuntime(3525):     at android.os.Handler.dispatchMessage(Handler.java:99)
    05-18 03:36:42.732: E/AndroidRuntime(3525):     at android.os.Looper.loop(Looper.java:137)
    05-18 03:36:42.732: E/AndroidRuntime(3525):     at android.app.ActivityThread.main(ActivityThread.java:5041)
    05-18 03:36:42.732: E/AndroidRuntime(3525):     at java.lang.reflect.Method.invokeNative(Native Method)
    05-18 03:36:42.732: E/AndroidRuntime(3525):     at java.lang.reflect.Method.invoke(Method.java:511)
    05-18 03:36:42.732: E/AndroidRuntime(3525):     at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793)
    05-18 03:36:42.732: E/AndroidRuntime(3525):     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560)
    05-18 03:36:42.732: E/AndroidRuntime(3525):     at dalvik.system.NativeStart.main(Native Method)
    05-18 03:36:42.732: E/AndroidRuntime(3525): Caused by: java.lang.NullPointerException
    05-18 03:36:42.732: E/AndroidRuntime(3525):     at android.app.LoadedApk.initializeJavaContextClassLoader(LoadedApk.java:379)
    05-18 03:36:42.732: E/AndroidRuntime(3525):     at android.app.LoadedApk.getClassLoader(LoadedApk.java:322)
    05-18 03:36:42.732: E/AndroidRuntime(3525):     at android.app.LoadedApk.makeApplication(LoadedApk.java:496)
    05-18 03:36:42.732: E/AndroidRuntime(3525):     ... 11 more
    05-18 03:36:56.010: D/gralloc_goldfish(3558): Emulator without GPU emulation detected.
    05-18 03:47:25.183: I/Choreographer(3558): Skipped 45 frames!  The application may be doing too much work on its main thread.
    05-18 03:47:39.080: D/gralloc_goldfish(3613): Emulator without GPU emulation detected.
    05-18 03:47:41.770: D/dalvikvm(3613): GC_CONCURRENT freed 84K, 7% free 2781K/2988K, paused 72ms+10ms, total 196ms
    05-18 03:47:41.770: D/dalvikvm(3613): WAIT_FOR_CONCURRENT_GC blocked 55ms
    05-18 03:47:45.579: D/dalvikvm(3613): GC_CONCURRENT freed 100K, 7% free 3083K/3300K, paused 5ms+20ms, total 226ms
    05-18 03:47:53.329: I/Choreographer(3613): Skipped 111 frames!  The application may be doing too much work on its main thread.

这意味着,在代码中的某个地方,如错误所述:在第379行,如果LoadedApk是您的类,则您试图访问未首先创建的对象或创建失败的对象,以及它持有Null而不是实际值或对象的对象。

您发布的是堆栈跟踪。这是对最近发生的事情的追踪,追溯到发生了什么让你到达那里

你需要反向阅读。你发布的第一行是最近发生的事情

你可以这样想:

Caused by: java.lang.NullPointerException at android.app.LoadedApk.initializeJavaContextClassLoader(LoadedApk.java:379)

我不认为赋值null是null指针异常的工作方式……这对我来说没有意义;我的所有文件都没有379行那么长,原因有二。首先,在代码的某个地方,赋值null并不是null指针赋值的方式。其次,您忽略了所问的整个问题,这是堆栈跟踪中条目的顺序,而不是这些条目的内容。@KenWhite,我认为您对第二部分的看法不正确,OP问题是:有人能帮我理解为什么我的日志开始出现错误,然后开始说我的模拟开始工作了吗。我只是指出,stacktrace的第二部分(仿真器开始运行的事实)与实际异常之间没有任何联系。好的:尽管你反对,第一个原因的否决票仍然存在。99.99999999%的统计数据是虚构的,当然,所有空指针异常都不是由在代码中使用空指针引起的。相同的百分比是由于尝试访问未首先创建的内容或创建失败的内容造成的,这与您分配Null的地方不同。非常好的解释。你自己写的吗+1、解释清楚@acdcjunior:是的。我以前烧伤过手指。事情就是这样发生的-嗯,这确实让我朝着正确的方向前进,谢谢:我还认为这包括了一条评论,其中有人提出了一个与我匹配的解决方案,即我必须确保在模拟器中我在主屏幕上,并且应用程序不会在手机上运行。
I feel pain in my finger.
Just before that, my finger touched a hot burner.
Just before that, my hand stopped moving.
Just before that, my hand was moving down toward the burner.
Just before that, my hand was over the stove.
Just before that, my hand was just in front of the stove.
Just before that, my hand was near the stove.
Just before that, my hand was near my body.
Just before that, my hand was by my side.