how to debug the jar files while developing the native extension for android

I'm having the same problem. I learned FB and Eclipse. I've read the tutorials, created an ane, and built it into a test app. I can debug my test app within FB 4.7 on my mobile device via USB. But there are bugs and they silently fail. Despite all my Log statements in my android java code, they won't output to the FB console. I'm blind, without even trace statements to help fix my ane. I've searched the internet and can't find anything. It must either be terribly obvious or arcane, because no one mentions it.

Can anyone tell me how to get trace out of an ane?

The Android reference claims debug and verbose priority are stripped out at runtime. I switched to Log.i() but still get nothing. I suppose for now I'll try throwing errors and see if I can report trace info that way if possible.

Anyone perhaps have a JUnit test that will mimic AIR using the ane jar file as an extension? Perhaps it will be easier to go full native until the android side is debugged.

Update Edit: Ok, now spending more time reading the Android developers website. I've found I can use logcat to get all kinds of useful system logs, including the log output of my embedded ane. I created a nice big command line window (180 char wide with a 500 deep buffer so I can scroll back through all the messages), then from the android platform tools directory I ran 'adb shell', then at the shell prompt $>logcat

Links to info that helped me:

http://developer.android.com/tools/debugging/index.html

http://developer.android.com/tools/help/logcat.html

Bump. This would be a VERY useful feature. As it stands, ANE is basically useless. It's buggy, silently dies, and has poor documentation. If you want to be taken seriously, ANE is a MUST, and it has to be robust and easy to use.