Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 314536 - Launch ticking 'Use shared library symbols for debugged applications' creates an un-killable launch
Summary: Launch ticking 'Use shared library symbols for debugged applications' creates...
Status: RESOLVED FIXED
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug-dsf-gdb (show other bugs)
Version: 7.0   Edit
Hardware: PC Linux-GTK
: P3 normal (vote)
Target Milestone: 7.0   Edit
Assignee: Marc Khouzam CLA
QA Contact: Marc Khouzam CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-26 13:10 EDT by James Blackburn CLA
Modified: 2010-05-29 07:23 EDT (History)
1 user (show)

See Also:

Attachments
errors in log (3.36 KB, text/plain)
2010-05-26 13:10 EDT, James Blackburn CLA 		no flags Details
Fix to hide option (1.57 KB, patch)
2010-05-29 06:10 EDT, Marc Khouzam CLA 		marc.khouzam: iplog-
Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description James Blackburn CLA 2010-05-26 13:10:19 EDT 
Created attachment 170053 [details]
errors in log

I ticked:
Debugger Tab > Shared Libraries > Use shared library symbols for debugged applications
to see what it does. When I run a C/C++ Application with this, it doesn't launch, and the process can't be terminated from the Debug View. There's no lingering GDB's to kill from the shell either.

You get the attached in the error log and an error dialog.
Comment 1 Marc Khouzam CLA 2010-05-26 14:14:55 EDT 
This option is meant for remote attach launches and multi-process.  I should probably disable it in other cases.

The launch should not be left in limbo like that though.
Comment 2 Marc Khouzam CLA 2010-05-26 14:52:54 EDT 
I've opened Bug 314554 about the launch being stuck and not being able to terminate it.
Comment 3 Marc Khouzam CLA 2010-05-29 06:06:08 EDT 
The "Use shared library symbols for debugged applications" was meant for targets that already support multi-process.  When this option is checked, we don't tell GDB about any binary as it will figure it out itself.  This was for GDB 7.0.

However, this whole GDB mechanism has been changed when it introduced multi-exec (which is multi-process which works on Linux) in GDB 7.1.  DSF-GDB does not support this new mechanism yet, but we are targetting it for the next CDT release (see bug 237306).

Until we figure out if we really need "Use shared library symbols for debugged applications" anymore, I will hide the option for 7.0 because having a hanging launch is pretty bad.

I am not aware of anyone using this feature for their own multi-process target.
Comment 4 Marc Khouzam CLA 2010-05-29 06:10:58 EDT 
Created attachment 170453 [details]
Fix to hide option

This is low risk so I committed it to HEAD
Comment 5 Marc Khouzam CLA 2010-05-29 06:12:46 EDT 
I'm marking this bug as fixed and we can revisit the whole "Use shared library symbols for debugged applications" option as part of bug 237306 for 8.0.

James, is that ok with you?
Comment 6 James Blackburn CLA 2010-05-29 06:16:52 EDT 
(In reply to comment #5)
> James, is that ok with you?

Looks good, thanks Marc!
Comment 7 CDT Genie CLA 2010-05-29 06:23:01 EDT 
*** cdt cvs genie on behalf of mkhouzam ***
Bug 314536: Hide "Use shared library symbols for debugged applications" as it makes normal launches fail.  We will revisit this option when we fully support multi-exec on Linux

[*] GDBSolibBlock.java 1.2 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/dsf-gdb/org.eclipse.cdt.dsf.gdb.ui/src/org/eclipse/cdt/dsf/gdb/internal/ui/launching/GDBSolibBlock.java?root=Tools_Project&r1=1.1&r2=1.2