From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24841 invoked by alias); 7 Jul 2004 16:12:58 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 24832 invoked from network); 7 Jul 2004 16:12:56 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 7 Jul 2004 16:12:56 -0000 Received: from drow by nevyn.them.org with local (Exim 4.34 #1 (Debian)) id 1BiF2C-0003ij-2P for ; Wed, 07 Jul 2004 12:12:36 -0400 Date: Wed, 07 Jul 2004 16:12:00 -0000 From: Daniel Jacobowitz To: gdb@sources.redhat.com Subject: Re: gdb 6.2 blockers Message-ID: <20040707161235.GA20681@nevyn.them.org> Mail-Followup-To: gdb@sources.redhat.com References: <40EADC2B.7080504@gnu.org> <40EC1628.8050207@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40EC1628.8050207@gnu.org> User-Agent: Mutt/1.5.5.1+cvs20040105i X-SW-Source: 2004-07/txt/msg00056.txt.bz2 On Wed, Jul 07, 2004 at 11:26:32AM -0400, Andrew Cagney wrote: > More edits: > > >1650: I suspect this is really a kernel race condition. > >I remember that Jeff was pointing out that the bug this tickles is a race > >condition (hence isn't always reproducable). The fix for NPTL involves > >kernel changes, I'm not sure about linuxthreads. > I couldn't get the test to fail on NPTL -> linuxthreads specific. Ditto; one failure mode on LinuxThreads is: (gdb) PASS: gdb.threads/manythreads.exp: info threads continue Continuing. PASS: gdb.threads/manythreads.exp: second continue (gdb) Quit (gdb) FAIL: gdb.threads/manythreads.exp: stop threads 2 We stop threads for no apparent reason and then the C-c is handled at the prompt. Another is: (gdb) PASS: gdb.threads/manythreads.exp: shell stty intr '^C' continue Continuing. PASS: gdb.threads/manythreads.exp: first continue /opt/src/gdb/src/gdb/lin-lwp.c:645: internal-error: wait_lwp: Assertion `lp->status == 0' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. FAIL: gdb.threads/manythreads.exp: stop threads 1 (GDB internal error) Jeff's presumably right about the race condition. Did he investigate at all? The error means the waitstatus state machine in lin-lwp is somehow broken. -- Daniel Jacobowitz