| Summary: | Launch ticking 'Use shared library symbols for debugged applications' creates an un-killable launch | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Tools] CDT | Reporter: | James Blackburn <jamesblackburn+eclipse> | ||||||
| Component: | cdt-debug-dsf-gdb | Assignee: | Marc Khouzam <marc.khouzam> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | Marc Khouzam <marc.khouzam> | ||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | pawel.1.piech | ||||||
| Version: | 7.0 | ||||||||
| Target Milestone: | 7.0 | ||||||||
| Hardware: | PC | ||||||||
| OS: | Linux-GTK | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
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. I've opened Bug 314554 about the launch being stuck and not being able to terminate it. 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. Created attachment 170453 [details]
Fix to hide option
This is low risk so I committed it to HEAD
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? (In reply to comment #5) > James, is that ok with you? Looks good, thanks Marc! *** 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 *** cdt cvs genie on behalf of mkhouzam *** Bug 314536; Typo [*] GDBSolibBlock.java 1.3 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.2&r2=1.3 |
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.