gdb/61: attaching to multithreaded program

haakon@oppdal.net haakon@oppdal.net
Wed Jun 13 23:08:00 GMT 2001


>Number:         61
>Category:       gdb
>Synopsis:       attaching to multithreaded program
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Jun 13 23:08:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     haakon@oppdal.net
>Release:        CVS -version, 2001-05-20
>Organization:
>Environment:
linux-2.4.4, glibc-2.2.2, gcc-3.0-20010430
>Description:
When attaching to a multithreaded program, only attaching to the first/main thread works. And that thread sometimes is missing info about the other threads. 
Attaching to a thread other than main results in this message:
Child process unexpectedly missing: No child processes.

Program terminated with signal ?, Unknown signal.
The program no longer exists.
After that, the thread process I try to attach to has status 'T' (traced) even when I quit gdb.

This may not be an gdb -issue, but rather a linuxthread-issue... I'm not sure, I'm not familiar with the inner workings of gdb. I also see the same problem with "strace -p <pid> " not being able to attach to the thread, but that may not be supposed to work?

Regards, HÃ¥kon Innerdal


>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the Gdb-prs mailing list