This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug threads/20743] can't usefully "continue" due to "ptrace: No such process" after gdb switches thread (gdb7.11.1 on FreeBSD 11)
- From: "jhb at FreeBSD dot org" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 22 Dec 2016 01:42:13 +0000
- Subject: [Bug threads/20743] can't usefully "continue" due to "ptrace: No such process" after gdb switches thread (gdb7.11.1 on FreeBSD 11)
- Auto-submitted: auto-generated
- References: <bug-20743-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20743
jhb at FreeBSD dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jhb at FreeBSD dot org
--- Comment #2 from jhb at FreeBSD dot org ---
I can confirm this, and I have a similar patch (but using is_exited(), and
patching both of the callbacks, but asserting that we never try to do a
single-resume of an exited thread).
The reason gdb switches to new threads when they are created is that we always
report a stop when a new thread arrives. I could change this to have it only
add the thread but not report a stop, but it gets kind of messy if you are
single-stepping across thread creation as in theory I would need to cache that
info down in the fbsd nat layer and PT_SUSPEND the new thread before doing my
own PT_CONTINUE.
--
You are receiving this mail because:
You are on the CC list for the bug.