Bug 182185 - When attaching to a runing/threaded process, only one thread is attached
Summary: When attaching to a runing/threaded process, only one thread is attached
Alias: None
Product: Fedora
Classification: Fedora
Component: gdb (Show other bugs)
(Show other bugs)
Version: 4
Hardware: i686 Linux
Target Milestone: ---
Assignee: Jan Kratochvil
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2006-02-20 21:47 UTC by U. George
Modified: 2008-03-10 04:04 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-03-10 04:04:56 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description U. George 2006-02-20 21:47:58 UTC
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

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
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.

Comment 1 Jan Kratochvil 2006-07-18 17:23:44 UTC
Unable to reproduce on:

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.

Comment 2 Jan Kratochvil 2006-08-16 00:07:13 UTC
Please update this Bug if the problem is still present in FC5 or FC6test2, it
does not appear to me so.

Comment 3 petrosyan 2008-03-10 04:04:56 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.