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 Problem starting gdbserver to debug android NDK application

Note: This was originally posted on 29th December 2011 at http://forums.arm.com

Hi Everyone,

I am facing problem when starting debug session for native code debugging using DS-5   CE,

This is what is shown:

   eclipse.buildId=M20110909-1335
java.version=1.6.0_26
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Framework arguments: -product org.eclipse.epp.package.cpp.product
Command-line arguments: -os linux -ws gtk -arch x86 -product org.eclipse.epp.package.cpp.product

Error
Wed Dec 28 20:51:17 EET 2011
Failed gdbserver configuration:
Timeout. PID not found!

com.arm.debugger.control.target.TargetControllerException: Failed gdbserver configuration:
Timeout. PID not found!
    at com.arm.debugger.control.target.TargetController.runGDB(TargetController.java:623)
    at com.arm.debugger.control.target.TargetController.setupAndroid(TargetController.java:108)
    at com.arm.debugger.control.target.TargetController.setupGdbServerOnTarget(TargetController.java:121)
    at com.arm.debugger.control.target.TargetController.setupTarget(TargetController.java:78)
    at com.arm.debugger.control.ConnectionController.doPreDebugServiceInitialization(ConnectionController.java:592)
    at com.arm.debugger.control.ConnectionController.doInitialize(ConnectionController.java:533)
    at com.arm.debugger.control.ConnectionController.manageThreadModelAndInitialize(ConnectionController.java:524)
    at com.arm.debugger.control.ConnectionController.manageConnectionCleanupAndInitialize(ConnectionController.java:510)
    at com.arm.debugger.control.ConnectionController.manageProgressResourceAndInitialize(ConnectionController.java:463)
    at com.arm.debugger.control.ConnectionController.initializeNonModelConnection(ConnectionController.java:435)
    at com.arm.debugger.control.ConnectionController.initialize(ConnectionController.java:410)
    at com.arm.debugger.control.ConnectionManager.createConnection(ConnectionManager.java:391)
    at com.arm.debugger.launcher.TargetLauncher.connect(TargetLauncher.java:70)
    at com.arm.debugger.launcher.TargetLauncher.launch(TargetLauncher.java:44)
    at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854)
    at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
    at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:928)
    at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1132)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

The set-up the environment is based on these guidelines:

http://infocenter.ar...h/CIHEEGJH.html

http://kernel.ozandroid.info/?p=83

I am on 32 bit Ubuntu 11.10 host and debugging is on avd API level 14

What could be the problem?

Thanks a lot in advance!

Parents

Nivelinn Pantev over 11 years ago

Note: This was originally posted on 9th January 2012 at http://forums.arm.com

Well, negative as well.

the application is running:
app_40 691 37 130940 34864 ffffffff 40011384 S com.example.neon

but:

eclipse.buildId=M20110909-1335
java.version=1.6.0_26
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Framework arguments: -product org.eclipse.epp.package.cpp.product
Command-line arguments: -os linux -ws gtk -arch x86 -product org.eclipse.epp.package.cpp.product

Error
Mon Jan 09 19:38:01 EET 2012
Failed gdbserver configuration:
Timeout. PID not found!

com.arm.debugger.control.target.TargetControllerException: Failed gdbserver configuration:
Timeout. PID not found!
at com.arm.debugger.control.target.TargetController.runGDB(TargetController.java:623)
at com.arm.debugger.control.target.TargetController.setupAndroid(TargetController.java:108)
at com.arm.debugger.control.target.TargetController.setupGdbServerOnTarget(TargetController.java:121)
at com.arm.debugger.control.target.TargetController.setupTarget(TargetController.java:78)
at com.arm.debugger.control.ConnectionController.doPreDebugServiceInitialization(ConnectionController.java:592)
at com.arm.debugger.control.ConnectionController.doInitialize(ConnectionController.java:533)
at com.arm.debugger.control.ConnectionController.manageThreadModelAndInitialize(ConnectionController.java:524)
at com.arm.debugger.control.ConnectionController.manageConnectionCleanupAndInitialize(ConnectionController.java:510)
at com.arm.debugger.control.ConnectionController.manageProgressResourceAndInitialize(ConnectionController.java:463)
at com.arm.debugger.control.ConnectionController.initializeNonModelConnection(ConnectionController.java:435)
at com.arm.debugger.control.ConnectionController.initialize(ConnectionController.java:410)
at com.arm.debugger.control.ConnectionManager.createConnection(ConnectionManager.java:391)
at com.arm.debugger.launcher.TargetLauncher.connect(TargetLauncher.java:70)
at com.arm.debugger.launcher.TargetLauncher$ConnectJob.run(TargetLauncher.java:99)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Cancel
Vote up 0 Vote down

Cancel

Reply

Nivelinn Pantev over 11 years ago

Note: This was originally posted on 9th January 2012 at http://forums.arm.com

Well, negative as well.

the application is running:
app_40 691 37 130940 34864 ffffffff 40011384 S com.example.neon

but:

eclipse.buildId=M20110909-1335
java.version=1.6.0_26
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Framework arguments: -product org.eclipse.epp.package.cpp.product
Command-line arguments: -os linux -ws gtk -arch x86 -product org.eclipse.epp.package.cpp.product

Error
Mon Jan 09 19:38:01 EET 2012
Failed gdbserver configuration:
Timeout. PID not found!

com.arm.debugger.control.target.TargetControllerException: Failed gdbserver configuration:
Timeout. PID not found!
at com.arm.debugger.control.target.TargetController.runGDB(TargetController.java:623)
at com.arm.debugger.control.target.TargetController.setupAndroid(TargetController.java:108)
at com.arm.debugger.control.target.TargetController.setupGdbServerOnTarget(TargetController.java:121)
at com.arm.debugger.control.target.TargetController.setupTarget(TargetController.java:78)
at com.arm.debugger.control.ConnectionController.doPreDebugServiceInitialization(ConnectionController.java:592)
at com.arm.debugger.control.ConnectionController.doInitialize(ConnectionController.java:533)
at com.arm.debugger.control.ConnectionController.manageThreadModelAndInitialize(ConnectionController.java:524)
at com.arm.debugger.control.ConnectionController.manageConnectionCleanupAndInitialize(ConnectionController.java:510)
at com.arm.debugger.control.ConnectionController.manageProgressResourceAndInitialize(ConnectionController.java:463)
at com.arm.debugger.control.ConnectionController.initializeNonModelConnection(ConnectionController.java:435)
at com.arm.debugger.control.ConnectionController.initialize(ConnectionController.java:410)
at com.arm.debugger.control.ConnectionManager.createConnection(ConnectionManager.java:391)
at com.arm.debugger.launcher.TargetLauncher.connect(TargetLauncher.java:70)
at com.arm.debugger.launcher.TargetLauncher$ConnectJob.run(TargetLauncher.java:99)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Cancel
Vote up 0 Vote down

Cancel

Children

No data