This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug threads/18127] threads spawned by infcall end up stuck in "running" state
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 05 May 2015 17:07:40 +0000
- Subject: [Bug threads/18127] threads spawned by infcall end up stuck in "running" state
- Auto-submitted: auto-generated
- References: <bug-18127-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18127
--- Comment #2 from Pedro Alves <palves at redhat dot com> ---
Thanks.
> quite often other threads run before the printing is finished
That means the pretty printer is calling functions in the inferior, which then
ends up being the same problem.
The workaround is to switch to one of the threads that GDB knows is stopped
(e.g., thread 22 in your case) and continue that one, or do "stepi" -- when
that step finishes, the threads' states sync up.
--
You are receiving this mail because:
You are on the CC list for the bug.