• Locked Locked
  • Replies 11 replies
  • Subscribers 120 subscribers
  • Views 6356 views
  • Users 0 members are here
Options
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
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
  • Note: This was originally posted on 26th April 2012 at http://forums.arm.com

    Just changing the two scripts (run.py and setup.py) didn't do the job so I've searched all .py files and modified in similar way all occurrences  of device to be empty. Again I think it partial worked.

    The first time I select to debug the application I see that the application is installed on the device, the it is executed but then I get the message: "Failed to communicate with gdbserver at localhost on port 5000. No data received. Failed to connect to the device" But in the LogCat pane I see my debug output messages.

    If I close the application and try for a second time then it seams it works, at some point the debugger stops at: 0x700057FD [debugger internal thumb] which I think is before entering my main application function. Unfortunately all breakpoints I have even though they are enabled don't work.

    For instance I have placed a break point inside a function where I output the message "Should stop at this breakpoint", well I see output at LogCat but never stops at the breakpoint.

    Did I do well by modifying all scripts?

    Files I also modified apart from: (run.py & setup.py)

    adb_common.py
    push_pull.py
    run_nostart.py
    setup_nocopy.py
Reply
  • Note: This was originally posted on 26th April 2012 at http://forums.arm.com

    Just changing the two scripts (run.py and setup.py) didn't do the job so I've searched all .py files and modified in similar way all occurrences  of device to be empty. Again I think it partial worked.

    The first time I select to debug the application I see that the application is installed on the device, the it is executed but then I get the message: "Failed to communicate with gdbserver at localhost on port 5000. No data received. Failed to connect to the device" But in the LogCat pane I see my debug output messages.

    If I close the application and try for a second time then it seams it works, at some point the debugger stops at: 0x700057FD [debugger internal thumb] which I think is before entering my main application function. Unfortunately all breakpoints I have even though they are enabled don't work.

    For instance I have placed a break point inside a function where I output the message "Should stop at this breakpoint", well I see output at LogCat but never stops at the breakpoint.

    Did I do well by modifying all scripts?

    Files I also modified apart from: (run.py & setup.py)

    adb_common.py
    push_pull.py
    run_nostart.py
    setup_nocopy.py
Children
No data