Red Hat Bugzilla – Bug 182185
When attaching to a runing/threaded process, only one thread is attached
Last modified: 2008-03-10 00:04:56 EDT
Description of problem: Because of a problem with thread_db, one has to start the threaded program as a regular executable. On another tty, u attach to the process with gdb pgm procID. This only attaches one ( of many threads ). Gdb is not aware of any of the other threads. Version-Release number of selected component (if applicable): How reproducible: I suspect always reproduceable. Steps to Reproduce: 1. get javasofts jdk. 2. run one of the demo's ( dont use gdb ) 3. try to attach to all the threads that are a part of the demo. There a few procID's. Actual results: u only get one of the many threads. u also dont get to observe the sigsegv fault that happened in another (unknown) thread ;-{ Expected results: maybe all the threads will be known to GDB? So when i 'c', gdb will catch one of the threads segfaulting. Additional info: i can help with the java demo setup, if need be.
Unable to reproduce on: FC5-i386 gdb-6.3.0.0-1.122 3188bedc75d4500f599558427b95156c /home/lace/arch/java/jdk-1_5_0_06-linux-i586-rpm.bin jdk/demo/jfc/Notepad/Notepad.jar Caught all the 12 threads on "attach" (compared with the list seen by "ps -eLf"). Apparently it was not crashing so the reproducibility test was not perfect.
Please update this Bug if the problem is still present in FC5 or FC6test2, it does not appear to me so.
The information we've requested above is required in order to review this problem report further and diagnose/fix the issue if it is still present. Since there have not been any updates to the report since thirty (30) days or more since we requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. Setting status to "INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report. Thank you in advance.