This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug threads/20743] can't usefully "continue" due to "ptrace: No such process" after gdb switches thread (gdb7.11.1 on FreeBSD 11)


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.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]