Error Debugging on 1.6

[rscott]

Attempted to use the debugger on Android 1.6, but my app crashed immediately.

I tried creating a new app (making no changes and adding no code) and deploying it to the emulator and it crashed again. The error is :-

HeapWorker thread shutting down
HeapWorker thread has shut down
JDWP shutting down net...
VM cleaning up
LinearAlloc 0x0 used 674660 of 4194304 (16%)
Start proc test.test for activity test.test/.main: pid=637 uid=10025 gids={3003, 3002, 1015}
java.lang.NoSuchFieldException: flags
   at java.lang.ClassCache.findFieldByName(ClassCache.java:510)
   at java.lang.Class.getDeclaredField(Class.java:693)
   at anywheresoftware.b4a.Msgbox.<clinit>(Msgbox.java:51)
   at test.test.main.onResume(main.java:176)
   at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1225)
   at android.app.Activity.performResume(Activity.java:3560)
   at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2838)


   at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:2866)
   at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2420)
   at android.app.ActivityThread.access$2100(ActivityThread.java:116)
   at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1794)
   at android.os.Handler.dispatchMessage(Handler.java:99)
   at android.os.Looper.loop(Looper.java:123)
   at android.app.ActivityThread.main(ActivityThread.java:4203)
   at java.lang.reflect.Method.invokeNative(Native Method)
   at java.lang.reflect.Method.invoke(Method.java:521)
   at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:549)
   at dalvik.system.NativeStart.main(Native Method)
Could not find method android.bluetooth.BluetoothAdapter.getDefaultAdapter, referenced from method anywheresoftware.b4a.debug.DebugConnector.<init>
VFY: unable to resolve static method 62: Landroid/bluetooth/BluetoothAdapter;.getDefaultAdapter ()Landroid/bluetooth/BluetoothAdapter;
VFY:  rejecting opcode 0x71 at 0x0029
VFY:  rejected Lanywheresoftware/b4a/debug/DebugConnector;.<init> (Lanywheresoftware/b4a/debug/DebugConnector$MessageHandler;ILjava/lang/String;)V
Verifier rejected class Lanywheresoftware/b4a/debug/DebugConnector;
Shutting down VM
threadid=3: thread exiting with uncaught exception (group=0x4001aa28)
Uncaught handler: thread main exiting due to uncaught exception
java.lang.VerifyError: anywheresoftware.b4a.debug.DebugConnector
   at anywheresoftware.b4a.debug.Debug.StartDebugging(Debug.java:101)
   at test.test.main.initializeProcessGlobals(main.java:258)
   at test.test.main.afterFirstLayout(main.java:80)
   at test.test.main.access$100(main.java:16)
   at test.test.main$WaitForLayout.run(main.java:72)
   at android.os.Handler.handleCallback(Handler.java:587)
   at android.os.Handler.dispatchMessage(Handler.java:92)
   at android.os.Looper.loop(Looper.java:123)
   at android.app.ActivityThread.main(ActivityThread.java:4203)
   at java.lang.reflect.Method.invokeNative(Native Method)
   at java.lang.reflect.Method.invoke(Method.java:521)
   at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:549)
   at dalvik.system.NativeStart.main(Native Method)
Sending signal. PID: 637 SIG: 3
threadid=7: reacting to signal 3
Unable to open stack trace file '/data/anr/traces.txt': Permission denied
Sending signal. PID: 637 SIG: 9
Process test.test (pid 637) has died.
WIN DEATH: Window{437ed3a8 test.test/test.test.main paused=false}

 

[eps]

Looks like the stack trace file either isn't there or isn't accessible..

Have you tried wiping user data first?

Is it a memory or SD card issue?

or have you made a change, but made your manifest file read only and it needs to update the permissions, that's what usually happens to me (I know I shouldn't do it this way, with the new editor, but it always seems to get it wrong with Admob permissions).

 

[rscott]

It's an emulated machine. If I create a new 2.3 or 4 emulator, they work perfectly.
Seems to be a specific issue with 1.6

I need the debug mode to track down another 1.6 specific issue..

 

[eps]

It's an emulated machine. If I create a new 2.3 or 4 emulator, they work perfectly.
Seems to be a specific issue with 1.6

I need the debug mode to track down another 1.6 specific issue..

Yes I understand that, but in your log you have :

"Unable to open stack trace file '/data/anr/traces.txt': Permission denied"

I think this is halting the execution, so you need to work out why it's permission denied. The virtual machines do not all set themselves up the same and possibly the 1.6 one you have has either run out of space, or doesn't actually have any space available, so then halts..

HTH

 

[Erel]

The debugger requires Android 2.0 or above.

 

[eps]

The debugger requires Android 2.0 or above.

Eh? But I've got an AVD that's 1.6 and can be debugged, or has this changed recently?

 

[Erel]

Starting from B4A v1.9 you can only debug with Android v2.0 or above.