From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17071 invoked by alias); 14 Sep 2011 15:04:24 -0000 Received: (qmail 17060 invoked by uid 22791); 14 Sep 2011 15:04:22 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 14 Sep 2011 15:04:07 +0000 Received: from nat-ies.mentorg.com ([192.94.31.2] helo=EU1-MAIL.mgc.mentorg.com) by relay1.mentorg.com with esmtp id 1R3r0Q-00008w-TW from pedro_alves@mentor.com ; Wed, 14 Sep 2011 08:04:07 -0700 Received: from scottsdale.localnet ([172.16.63.104]) by EU1-MAIL.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 14 Sep 2011 16:04:05 +0100 From: Pedro Alves To: gdb@sourceware.org Subject: Re: Thread exit error : gdb7.2 in FreeBSD (built from ports) Date: Wed, 14 Sep 2011 15:04:00 -0000 User-Agent: KMail/1.13.6 (Linux/2.6.38-11-generic; KDE/4.7.0; x86_64; ; ) Cc: Jusctsch References: <32463912.post@talk.nabble.com> In-Reply-To: <32463912.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201109141604.02961.pedro@codesourcery.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: 2011-09/txt/msg00044.txt.bz2 On Wednesday 14 September 2011 15:26:33, Jusctsch wrote: > > Hello all, > I have been running into a particularly interesting issue. > When a thread exits in the application gdb is running, that exit doesn't > seem to propagate in some of the fields in gdb. In many cases, this will end > up crashing gdb (failing a thread_info=NULL gdbassert). > > [Thread 803855580 (LWP 100241 Foo) exited] > error: Invalid selected thread. > thread.c:583: internal-error: set_running: Asser tion > `tp->state_ != THREAD_EXITED' failed. > A problem internal to GDB has been detected, > further debugging may prove unreliable. > Quit this debugging session? (y or n) [answered Y; input > not from terminal] > thread.c:583: internal-error: set_running: Asser tion > `tp->state_ != THREAD_EXITED' failed. > A problem internal to GDB has been detected, > further debugging may prove unreliable. > Create a core file of GDB? (y or n) [answered Y; input not > from terminal] > > Is this a symptom of FreeBSD and some libraries? It's a gdb bug. We'd need more context to understand the problem. You can debug gdb with gdb, and put a breakpoint on `error' to catch that "error:", for example. Where's that coming from? Sounds like your port has local changes compared to the pristine FSF version? > Or is this a gross gdb issue? -- Pedro Alves