From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 14 14:49:08 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EECD51065767 for ; Wed, 14 Sep 2011 14:49:08 +0000 (UTC) (envelope-from schumjs@gmail.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id CAFDF8FC16 for ; Wed, 14 Sep 2011 14:49:08 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1R3qTX-0000FF-5j for freebsd-hackers@freebsd.org; Wed, 14 Sep 2011 07:30:07 -0700 Date: Wed, 14 Sep 2011 07:30:07 -0700 (PDT) From: John Schumacher To: freebsd-hackers@freebsd.org Message-ID: <1316010607171-4803024.post@n5.nabble.com> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: Problem with running simple pthreads program under gdb-7.2 (Invalid selected thread) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Sep 2011 14:49:09 -0000 These replies seemed to dance around the actual issue, I assume this wasn't resolved? I have been seeing this lately in gdb7.2 built from ports, and was curious as to what the real issue was. excerpt: [Thread 803855580 (LWP 100241 IPC UDP Socket) ex ited] 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] I encountered this in: get_current_frame(~) I don't think the current_inferior changes after a thread exits. Which could be okay, but I've noticed that the thread_info for this particular current_inferior doesn't always exist... Meaning that any time that a current_inferior ptid leads to a NULL thread_info [via find_thread_ptid(~)], we will get hosed on an assert. Any thoughts? -- View this message in context: http://freebsd.1045724.n5.nabble.com/Problem-with-running-simple-pthreads-program-under-gdb-7-2-Invalid-selected-thread-tp4426179p4803024.html Sent from the freebsd-hackers mailing list archive at Nabble.com.