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

Bug 343449

Summary: The state of the process in the debug view is not consistent with the state of the Resume and Suspend buttons when I debug multiple processes in GDB.
Product: [Tools] CDT Reporter: Dobrin Alexiev <dalexiev>
Component: cdt-debug-dsf-gdbAssignee: Project Inbox <cdt-debug-dsf-gdb-inbox>
Status: CLOSED DUPLICATE QA Contact: Marc Khouzam <marc.khouzam>
Severity: normal    
Priority: P3 CC: cdtdoug, pawel.1.piech
Version: 8.0   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Dobrin Alexiev CLA 2011-04-20 14:40:56 EDT 
Build Identifier: The latest DSF-GDB as of April 15, 2011

Ubuntu – gdb 7.2 
Create a program test that does fork() and then goes to infinite look. 
Debug the program. 
Make sure the debugger is NOT in non-stop mode. 
Resume the program so the fork() command is executed. 
Suspend the program. 
From the debug view’s “connect to  a process” green button attach to the seconds instance of the test program. 
	The program will appear in the debug view as suspended. 
Select a thread from the second program. 
Resume the second program. 
	The second program becomes running. That’s OK. 
Select a thread from the first program which appears suspended. 
See how the Run and Suspend but didn’t update. 

I was expecting the state of the first program in the debug view ( the pause decoration) to be consistent with the state of the Resume and Suspend buttons. 


Reproducible: Always

Steps to Reproduce:
see details.
Comment 1 Marc Khouzam CLA 2011-04-20 14:54:12 EDT 
Could this be a duplicate of Bug 337897?

Further, I believe now that we will not be able to support multi-process with all-stop at all.  I just posted a question to the gdb mailing list to confirm:
http://sourceware.org/ml/gdb/2011-04/msg00123.html
Comment 2 Dobrin Alexiev CLA 2011-04-20 15:11:43 EDT 
> Could this be a duplicate of Bug 337897?
I think so too.
Comment 3 Marc Khouzam CLA 2011-04-20 15:15:01 EDT 

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