From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7663 invoked by alias); 14 Sep 2011 14:41:03 -0000 Received: (qmail 7655 invoked by uid 22791); 14 Sep 2011 14:41:02 -0000 X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED,RP_MATCHES_RCVD,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 14 Sep 2011 14:40:02 +0000 Received: from isper.nabble.com ([192.168.236.156]) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1R3qd8-0001Ko-7r for gdb@sourceware.org; Wed, 14 Sep 2011 07:40:02 -0700 Message-ID: <32464063.post@talk.nabble.com> Date: Wed, 14 Sep 2011 14:41:00 -0000 From: Jusctsch To: gdb@sourceware.org Subject: Re: Thread exit error : gdb7.2 in FreeBSD (built from ports) In-Reply-To: <32463912.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <32463912.post@talk.nabble.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/msg00043.txt.bz2 I noticed this 'bad' behavior only in standard console gdb. The asserts do not happen in gdb-mi mode. 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? Or is this a gross gdb > issue? > > -- View this message in context: http://old.nabble.com/Thread-exit-error-%3A-gdb7.2-in-FreeBSD-%28built-from-ports%29-tp32463912p32464063.html Sent from the Sourceware - gdb list mailing list archive at Nabble.com.