Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] Use CDT debugger to attach to a running process

In the Debugger tab in teh Main subtab, you have the specification of the GDB process you want to run.
By default it is 'gdb'.  Unless 'gdb' is in your patch, it won't work and you'll get the error that you mention
You can replace the default with the full path that points to your GDB on the host machine.
 
Don't use GDB 7.1 as there is a bug in CDT right now: https://bugs.eclipse.org/bugs/show_bug.cgi?id=311965
Use GDB 7.0 or 6.8 should work fine.
 
Marc
 


From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Xuan Chen
Sent: Friday, June 25, 2010 2:47 PM
To: CDT General developers list.
Subject: [cdt-dev] Use CDT debugger to attach to a running process


Hi,

This is related to a question I posted a while ago...

http://dev.eclipse.org/mhonarc/lists/cdt-dev/msg17803.html

I tried the steps now, and had problem with using CDT debugger to attach a running process (gdbserver version is 7.1).  The version of CDT I used is 7.0 (probably not the final driver,  but RC3 or later driver).

Steps:
**********************************************
Run command "gdbserver --multi :10000" on the host.  I got message "Listening on port 10000".

Create a C/C++ Attach to Application launch configuration, and click on the hyperlink at the bottom of the Main page.  Choose GDB (DSF) Attach to Process Launcher option.

Select an existing project.

Swtich to Debugger tab, and choose "gdbserver" from the Debugger drop down.  I can see the "Connection" tab now.

Switch to "Connection" tab.  Change "Type" to TCP.  Enter my host name, and the Port number, which is 10000, "Apply".  (I did not see any Connect button in this page).

Click Debug.  But I got error: "Launching new_configuration has encounter a problem.  Error while launching command: gdb --verion. "
******************************************

I am not sure why the launching command is "gdb" here.  It seems to me it used the "GDB debugger" value from the main page of "Debugger" tab.  Is it the right behaviour?  Any steps I execute which are not correct here?  Thanks.


Thanks,

Xuan Chen,  Problem Determination Tools for IBM i
(905) 413-3769 T/L 313-3769
xuanchen@xxxxxxxxxx


Back to the top