Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 280626 - [launch] Launch cannot be terminated if inferior was never started and GDB is killed
Summary: [launch] Launch cannot be terminated if inferior was never started and GDB is...
Status: RESOLVED FIXED
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug-dsf-gdb (show other bugs)
Version: 6.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 8.0   Edit
Assignee: Marc Khouzam CLA
QA Contact: Marc Khouzam CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-17 11:04 EDT by Marc Khouzam CLA
Modified: 2011-05-17 12:00 EDT (History)
2 users (show)

See Also:

Attachments
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 Marc Khouzam CLA 2009-06-17 11:04:39 EDT 
If the FinalLaunchSequence fails, GDB will be terminated.  However, the inferior was never actually started (since it is the next to last step of the finalLaunchSequence).  The Launch in the debug view can be seen as running and I am not able to terminate it.  (I made the launch sequence fail by putting an invalid path in the MIEnvironmentCD command, as was seen in bug 263689) 

Another way to reproduce this is to comment out the call to start the inferior in the FinalLaunchSequence, which will prevent from starting the inferior.  Then, terminate GDB from the launch or terminate the entire launch.  We are then stuck with a launch that cannot be terminated because the inferior process cannot be terminated.

I think this has something to do with the fact that we added a RuntimeProcess to the launch with no valid process behind it.  RuntimeProcess has trouble marking itself as terminated because the streams cannot be closed or something like that
Comment 1 Marc Khouzam CLA 2011-05-17 12:00:07 EDT 
This has been fixed along the way.