Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Categories
- All Discussions1,524
- General534
- Graphics109
- GPU Computing419
- Mobile141
- Pro Graphics163
- Tools158
Tags in this Discussion
- android 101
- tegra-toolkit 29
- android-development-pack 25
- froyo 8
- nvidia-debug-manager 7
Delay in JNI debugging. Early breakpoints not hit unless ...
-
Hi,
First, thanks for the awesome devpack and debugger. There are quite a few solutions available like ARM DS-5, Sequoyah and WinDGB but none of those worked well or at all for that matter.
Now I do have a problem with the debugger. I tried to debug the hello-jni sample, set some breakpoints and started debugging. The application ran, the debugger connected but no breakpoints (in the C code) were hit. Now I figured out that the breakpoints and some other debug data is send over to the gdbserver after the debugging connection is established and the application started running. So to work around this Issue I have set a breakpoints in java code (which thankfully works aside c breakpoints :D ) at System.loadLibrary("..."); Causing the application to halt there, giving the server the time to receive its data in order to break at the right spots.
Now it all works. My question: Will this be fixed somehow in the future? For example preventing the application from running before all the debug data is sent over?
The device I use is a HTC Hero running Cyanogenmod 6.2 since the debugger requires atleast froyo.
Thanks in advance,
Wouter