Community
Participate
Working Groups
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.
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
> Could this be a duplicate of Bug 337897? I think so too.
*** This bug has been marked as a duplicate of bug 337897 ***