[Bug threads/19422] New: in non-stop mode, gdb does not print thread which stops

["tromey at sourceware dot org" <sourceware-bugzilla at sourceware dot org>]

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

            Bug ID: 19422
           Summary: in non-stop mode, gdb does not print thread which
                    stops
           Product: gdb
           Version: unknown
            Status: NEW
          Severity: normal
          Priority: P2
         Component: threads
          Assignee: unassigned at sourceware dot org
          Reporter: tromey at sourceware dot org
  Target Milestone: ---

I'm using non-stop mode to debug a situation where a crash occurs
in some sub-process.

I use this command to enter multi-inferior "mode":

define gomulti
  set detach-on-fork off
  set non-stop on
  set pagination off
end

I have "set print thread-events on".

Then when debugging I see:

Program received signal SIGSEGV, Segmentation fault.
0x00007fffeebd0dbc in nsXPConnect::GetRuntime (this=0x0) at
/home/tromey/firefox-git/gecko/js/xpconnect/src/xpcprivate.h:264
264         XPCJSRuntime* GetRuntime() {return mRuntime;}


Note that there is nothing here to indicate which thread cause the signal.

gdb doesn't select this thread, either (documented non-stop behavior -- though
perhaps not ideal).

In the end I was able to find the affected thread using "info thread"
and searching for the thread which did not say "(running)".

However, at the very least, in non-stop mode gdb should say which
thread is stopping.

-- 
You are receiving this mail because:
You are on the CC list for the bug.