From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4355 invoked by alias); 12 Aug 2008 21:10:40 -0000 Received: (qmail 4346 invoked by uid 22791); 12 Aug 2008 21:10:39 -0000 X-Spam-Check-By: sourceware.org Received: from outbound-mail-136.bluehost.com (HELO outbound-mail-136.bluehost.com) (67.222.39.26) by sourceware.org (qpsmtpd/0.31) with SMTP; Tue, 12 Aug 2008 21:09:51 +0000 Received: (qmail 23059 invoked by uid 0); 12 Aug 2008 21:09:45 -0000 Received: from unknown (HELO box166.bluehost.com) (69.89.25.166) by outboundproxy4.bluehost.com with SMTP; 12 Aug 2008 21:09:45 -0000 Received: from c75.152.91-94.clta.globetrotter.net ([75.152.91.94] helo=[192.168.128.28]) by box166.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1KT17h-0003ly-1k; Tue, 12 Aug 2008 15:09:45 -0600 Message-ID: <48A1FBE3.5090702@harfangmicro.com> Date: Thu, 14 Aug 2008 09:10:00 -0000 From: Marc Ferland User-Agent: Thunderbird 2.0.0.14 (X11/20080511) MIME-Version: 1.0 To: Marc Ferland , gdb@sourceware.org Subject: Re: Assert in linux_nat_resume References: <48A1E2C4.7020007@harfangmicro.com> <20080812192948.GA23036@caradoc.them.org> In-Reply-To: <20080812192948.GA23036@caradoc.them.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Identified-User: {651:box166.bluehost.com:harfangm:harfangmicro.com} {sentby:smtp auth 75.152.91.94 authed with mferland@harfangmicro.com} X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-08/txt/msg00170.txt.bz2 Daniel Jacobowitz wrote: > On Tue, Aug 12, 2008 at 03:21:40PM -0400, Marc Ferland wrote: >> I'm pretty sure it has something to do with my program but I don't know >> where to start (Debugging with printf() is a rather tedious task!). Any >> help would be greatly appreciated. > > The first thing to try is definitely a snapshot of current CVS GDB. > I tried with 6.8.50.20080812-cvs seems to have a similar problem. [New LWP 29169] linux-nat.c:1669: internal-error: linux_nat_resume: Assertion `lp != NULL' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. After further testing, this seems to happen only when I have a breakpoint somewhere inside a thread. The first time I hit the breakpoint everything is fine. But if I exit a thread and recreate it, I get the previously mentioned message. I also found a workaround: - The first time I hit the breakpoint, I delete it; - I place a breakpoint on the pthread_join() call for this thread; - When I break on the pthread_join() call, I recreate the breakpoint inside the thread; This way, I'm able to break inside the thread every time I create it (pthread_create()). Marc