This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
Re: threads/2383: internal-error: linux_nat_wait: Assertion`iterate_over_lwps (running_callback, NULL)' failed.
- From: Atsushi Nemoto <anemo at mba dot ocn dot ne dot jp>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 1 Mar 2008 13:48:02 -0000
- Subject: Re: threads/2383: internal-error: linux_nat_wait: Assertion`iterate_over_lwps (running_callback, NULL)' failed.
- Reply-to: Atsushi Nemoto <anemo at mba dot ocn dot ne dot jp>
The following reply was made to PR threads/2383; it has been noted by GNATS.
From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
To: drow@false.org
Cc: gdb-gnats@sourceware.org
Subject: Re: threads/2383: internal-error: linux_nat_wait: Assertion
`iterate_over_lwps (running_callback, NULL)' failed.
Date: Sat, 01 Mar 2008 22:46:42 +0900 (JST)
On Fri, 29 Feb 2008 11:50:18 -0500, Daniel Jacobowitz <drow@false.org> wrote:
> So you've single-stepped a thread until its exit, while it was the
> only thread running. Is that correct?
Yes.
> It seems like we ought to inform the user when this happens, not
> suddenly run somewhere else.
Hmm... Thank you, it might be better. But how to do that exactly?
---
Atsushi Nemoto