Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 358438 - -gdb-exit can be sent too early resulting in other commands which should be processed before arriving after
Summary: -gdb-exit can be sent too early resulting in other commands which should be p...
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug-dsf-gdb (show other bugs)
Version: 8.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-21 11:00 EDT by Daniel Thomas CLA
Modified: 2020-09-04 15:26 EDT (History)
2 users (show)

See Also:

Attachments
Patch adding delayedQueueCommand to AbstractMIControl and using it in GDBControl* (8.66 KB, patch)
2011-09-21 11:01 EDT, Daniel Thomas CLA 		no flags 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 Daniel Thomas CLA 2011-09-21 11:00:35 EDT 
Build Identifier: 

When -gdb-exit is sent by GDBControl(_7_0) in terminate(RequestMonitor) using createMiGDBExit it can arrive before other commands which should be sent first arrive. For example when the inferior has just exited and this is the reason why terminate is being called "-data-evaluate-expression $_exitcode" needs to be sent to check the exit code of the just terminated inferior but this can arrive after -gdb-exit and so not return correctly.
To fix this wait two executor dispatch cycles before sending the -gdb-exit.

I have a patch to do this.

Reproducible: Always
Comment 1 Daniel Thomas CLA 2011-09-21 11:01:50 EDT 
Created attachment 203783 [details]
Patch adding delayedQueueCommand to AbstractMIControl and using it in GDBControl*