Arm Community
Site
Search
User
Site
Search
User
Support forums
Arm Development Studio forum
DS-5 Android - Problem debugging on a device
Jump...
Cancel
Locked
Locked
Replies
11 replies
Subscribers
119 subscribers
Views
6662 views
Users
0 members are here
Options
Share
More actions
Cancel
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion
DS-5 Android - Problem debugging on a device
iosif hamlatzis
over 12 years ago
Note: This was originally posted on 19th April 2012 at
http://forums.arm.com
I've finally managed to make the emulator work and now can debug my game on it. Thank you.
As I don't have an actual android device, I've installed an experimental version of ICS on my HP TouchPad. It seams everything works all right. I can use the adb utility provided with the SDK to connect to the device with no problem. But I cannot debug from inside eclipse under windows on the actual device.
I created a second debug configuration for the device and selected my device in the Connection tab at the combo-box, but after a while I receive a message that eclipse cannot connect to the device. This is strange as I have no problem with the connection. Under a dos window using the adb command I can see I can connect, I even can shell into the device.
Parents
Albert Cano Camps
over 12 years ago
Note: This was originally posted on 29th April 2012 at
http://forums.arm.com
Hi Hamlatzis,
Thanks, your ps output is very useful. It shows us that your application is stopped (T on column 8) but any gdbserver instance is attached to your process, which may imply that gdbserver has attached to your app but somehow afterwards has died.
DS-5 ships two versions of gdbserver: gdbserver-stat-7.1 a statically linked version of gdbserver and gdbserver-dyna-7.1 that is built to dynamically link against the libraries on the Android target. Please, if you have been using static, now use dynamic, or if you have been using dynamic, now try static,... you could also try the gdbserver shipped in NDK. From our experience in production devices, dynamic linked is more likely to work.
Thanks,
Albert.
Cancel
Vote up
0
Vote down
Cancel
Reply
Albert Cano Camps
over 12 years ago
Note: This was originally posted on 29th April 2012 at
http://forums.arm.com
Hi Hamlatzis,
Thanks, your ps output is very useful. It shows us that your application is stopped (T on column 8) but any gdbserver instance is attached to your process, which may imply that gdbserver has attached to your app but somehow afterwards has died.
DS-5 ships two versions of gdbserver: gdbserver-stat-7.1 a statically linked version of gdbserver and gdbserver-dyna-7.1 that is built to dynamically link against the libraries on the Android target. Please, if you have been using static, now use dynamic, or if you have been using dynamic, now try static,... you could also try the gdbserver shipped in NDK. From our experience in production devices, dynamic linked is more likely to work.
Thanks,
Albert.
Cancel
Vote up
0
Vote down
Cancel
Children
No data