From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21368 invoked by alias); 7 Jul 2008 16:01:14 -0000 Received: (qmail 21324 invoked by uid 22791); 7 Jul 2008 16:01:07 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 07 Jul 2008 16:00:42 +0000 Received: (qmail 11434 invoked from network); 7 Jul 2008 16:00:40 -0000 Received: from unknown (HELO orlando.local) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 7 Jul 2008 16:00:40 -0000 From: Pedro Alves To: gdb@sourceware.org, Dmitry Smirnov Subject: Re: How to catch GDB crash Date: Mon, 07 Jul 2008 16:01:00 -0000 User-Agent: KMail/1.9.9 References: <200807071528.57718.pedro@codesourcery.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807071700.38268.pedro_alves@portugalmail.pt> 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-07/txt/msg00042.txt.bz2 A Monday 07 July 2008 16:47:26, Dmitry Smirnov wrote: > Perhaps, "info threads" is fixed. But since both "info threads" and > "running" problems were [most probably] caused by the "main thread > registering" fix, maybe it is better to investigate "^running" problem > before submission? What if they are connected? ;-) I seriously doubt they are connected. The code to output "^running" has nothing to do with having threads or not. > I have to say, that my goal is not just report issues, I would like to help > fixing them. Welcome on board! We need all the help we can get. > Unfortunately, I do not have much time to learn GDB, so I'm > just asking for hints: what can I do to discover the root cause. The best way is to do a binary search on the CVS HEAD sources, to find the patch that caused your issue. > For > example, who is responding "^running"? What functions/files should I debug > to figure out the problem? Grepping for "^running" should get you there. See here, your issue was most likelly introduced by this: http://sourceware.org/ml/gdb-patches/2008-06/msg00247.html -- Pedro Alves