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/19422] in non-stop mode, gdb does not print thread which stops


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

--- Comment #4 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Pedro Alves from comment #3)

> Is this along the lines of what you'd expect?

Very nice, that would be super to have.

FWIW I'm very much in favor of having per-inferior thread numbering.
The current situation is very confusing ... in fact while debugging
I got confused by it, even though I know about the current behavior.
One issue is that "info thread" doesn't give any indication of the
thread/inferior correspondence.

One final thing, which should maybe be a separate bug -- in my case
I just did "run".  When using a foreground continue like this, I
would expect gdb to select the thread of the first stop.  At least,
I'd expect this for "run" and "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]