public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
To: nobody@sources.redhat.com
Cc: gdb-prs@sources.redhat.com,
Subject: Re: threads/2383: internal-error: linux_nat_wait: Assertion `iterate_over_lwps (running_callback, NULL)' failed.
Date: Fri, 29 Feb 2008 16:28:00 -0000	[thread overview]
Message-ID: <20080229162801.22599.qmail@sourceware.org> (raw)

The following reply was made to PR threads/2383; it has been noted by GNATS.

From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
To: gdb-gnats@sources.redhat.com, nobody@sources.redhat.com
Cc:  
Subject: Re: threads/2383: internal-error: linux_nat_wait: Assertion
 `iterate_over_lwps (running_callback, NULL)' failed.
Date: Sat, 01 Mar 2008 01:23:06 +0900 (JST)

 I confirmed this problem is still in gdb-6.7.50.20080222.
 
 At that point, it seems gdb assume other threads are resumed, but this
 assumption is not true with scheduler-locking.
 
 With this patch, I can avoid the internal error.  Is this reasonable?
 
 --- gdb-6.7.50.20080222/gdb/linux-nat.c	2008-01-30 07:47:20.000000000 +0900
 +++ gdb/gdb/linux-nat.c	2008-03-01 01:10:57.000000000 +0900
 @@ -2138,6 +2138,9 @@ retry:
  	         ignored.  */
  	      if (num_lwps > 0)
  		{
 +		  /* If lwps were stopped (by schedlock), resume them. */
 +		  if (!iterate_over_lwps (running_callback, NULL))
 +		    iterate_over_lwps (resume_callback, NULL);
  		  /* Make sure there is at least one thread running.  */
  		  gdb_assert (iterate_over_lwps (running_callback, NULL));
  


             reply	other threads:[~2008-02-29 16:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-29 16:28 Atsushi Nemoto [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-03-01 14:58 Daniel Jacobowitz
2008-03-01 13:48 Atsushi Nemoto
2008-02-29 16:58 Daniel Jacobowitz
2008-01-26 15:48 Atsushi Nemoto
2007-12-13 16:58 anemo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080229162801.22599.qmail@sourceware.org \
    --to=anemo@mba.ocn.ne.jp \
    --cc=gdb-prs@sources.redhat.com \
    --cc=nobody@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).