This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug threads/21117] Occasional wrong thread numbering when following an exec
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 09 Feb 2017 14:02:20 +0000
- Subject: [Bug threads/21117] Occasional wrong thread numbering when following an exec
- Auto-submitted: auto-generated
- References: <bug-21117-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21117
--- Comment #2 from Pedro Alves <palves at redhat dot com> ---
Note that this isn't a case of a small race window. We have tests that
exercise the case of the leader thread really exits before its child threads.
In which case the leader remains zombie until the children exit. But if one of
the children execs instead, then the leader reappears then.
It may be that the best fix for all of this is to stop deleting the leader
thread when we detect it as zombie, but instead teach the core of gdb about
that state: the thread exists, but you can't do anything with it other than
collect exit status -- and leave the thread around. Easier to do when you
consider only native debugging. Not so simple when you consider target remote
/ RSP too.
--
You are receiving this mail because:
You are on the CC list for the bug.