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 gdb/12702] gdb can hang waiting for thread group leader


https://sourceware.org/bugzilla/show_bug.cgi?id=12702

Pedro Alves <palves at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |palves at redhat dot com

--- Comment #10 from Pedro Alves <palves at redhat dot com> ---
This is now fixed on GDBserver too.

  https://sourceware.org/ml/gdb-patches/2014-02/msg00826.html

I've left out the original "[PATCH 5/5] Add TARGET_WAITKIND_NO_RESUMED support
to the RSP" at https://sourceware.org/ml/gdb-patches/2014-01/msg00897.html ,
because I worried about races in non-stop mode.  Assume N is the new stop reply
for TARGET_WAITKIND_NO_RESUMED, and say, the traffic goes like this:

(no thread was resumed before #1)

GDB sends two steps in a row.

 #1 -> vCont;s:555
 #2 <- OK

(555 exits)

 #3 <- %Stop:N   (no more resumed threads left)

 #4 -> vCont;s:666
 #5 <- OK

And now GDB goes and processes #3, and mistakenly believes no thread is left
running on the target, while in fact, 666 is left running.

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