This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug threads/19461] strange "info thread" behavior in non-stop
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 14 Jan 2016 18:17:45 +0000
- Subject: [Bug threads/19461] strange "info thread" behavior in non-stop
- Auto-submitted: auto-generated
- References: <bug-19461-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19461
--- Comment #3 from Pedro Alves <palves at redhat dot com> ---
On 01/14/2016 06:05 PM, tromey at sourceware dot org wrote:
> The backtrace isn't very interesting. It's appended.
Yeah.
> If you want an infrun log, I can provide it, though it will be
> pretty voluminous I think.
I don't mind size. If you attach it, I'll take a look.
I'd prefer "set debug lin-lwp 1" + "set debug infrun 1", even.
> Here's the thread_info for the thread issuing the error:
>
> (gdb) p *$
> $3 = {
> executing = 1,
> resumed = 1,
> state = THREAD_STOPPED,
> refcount = 0,
There you go, THREAD_STOPPED, but somehow marked executing.
> trap_expected = 0,
> proceed_to_finish = 0,
> in_infcall = 0,
While in_infcall is 0...
It's likely that the thread really is running.
'cat /proc/PID/status | grep State' would show.
--
You are receiving this mail because:
You are on the CC list for the bug.