Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 278623

Summary: [run control] Resuming differently based on debug context
Product: [Tools] CDT Reporter: Marc Khouzam <marc.khouzam>
Component: cdt-debug-dsf-gdbAssignee: Project Inbox <cdt-debug-dsf-gdb-inbox>
Status: CLOSED DUPLICATE QA Contact: Marc Khouzam <marc.khouzam>
Severity: enhancement    
Priority: P3 CC: pawel.1.piech
Version: 6.0   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Marc Khouzam CLA 2009-06-01 10:40:18 EDT 
This bug applies to all-stop GDB (every pre 7.0, and all-stop 7.0)

Currently when resuming or stepping, the same GDB command is used independently of the debug context.  This means that when a thread is selected and the user resumes it, all threads are resumed.

GDb has the command 'set scheduler-locking on' which allows to keep every things stopped, except the one that is being resumed.  Using this we could offer the following:

1- if a stack or thread is selected, only resume that thread
2- if the process is selected, resume all threads of the process
3- for multi-process, if the launch is selected, resume all threads of all processes (this may require a new setting that is being proposed in GDB, set schedule-multiple off, see http://sourceware.org/ml/gdb-patches/2009-05/msg00647.html)
Comment 1 Marc Khouzam CLA 2011-05-17 16:09:15 EDT 

*** This bug has been marked as a duplicate of bug 339882 ***