07-16-2010 12:27 PM
I'm trying to debug an application on device. I had some initial success, but lately the device reboots when the debugger tries to launch the application. The application gets installed, and I can run it from the device after the device reboots, but so far I'm unable to get it to run under the debugger.
Eclipse: Galileo (3.5.2)
Blackberry Java Plug-in: 220.127.116.11004161203-16
Blackberry SDK: 18.104.22.168
Solved! Go to Solution.
07-19-2010 10:30 AM
Please refer to this post: http://supportforums.blackberry.com/t5/Testing-and
07-19-2010 12:15 PM
Thanks for your reply. I came across that post last week. Tried it and still had problems. This morning I tried again. I uninstalled the application. Then pulled the battery to start up clean. When I tried to launch the application from Eclipse, I saw the same reboot problem. The application does get installed, and I can run it from the device after the reboot.
I have some other test applications that I can install and debug. The application in question is getting large, and I saw some posts indicating that larger applications might be problematic and cause a reboot. Is there anything I can do to work around this problem? Is there a way to skip the install step (since the application is already installed), and just launch the application and attach the debugger? Alternatively, can I attach the debugger to an already running application? Right now I'm totally unable to debug on device.
07-27-2010 02:03 PM
I believe I've found a solution to this problem. I had tried the suggestion of deleting the application from Options | Applications on the device. Turns out this did not completely remove the application. Some library modules remained behind. I was able to delete these from Desktop Manager. This is a somewhat cumbersome process, but it gets me unblocked for on device debugging.
I hope that RIM will provide us with a better debugging experience in the future. It would be nice if the device reset weren't required, but I suppose it is in some scenarios. For these the debugger should tolerate the delay in connecting due to the reset. It would also be nice to be able to attach the debugger to a running application. IIRC, the was available in the old JDE SDK.