From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21120 invoked by alias); 31 Aug 2006 10:30:57 -0000 Received: (qmail 21111 invoked by uid 22791); 31 Aug 2006 10:30:56 -0000 X-Spam-Check-By: sourceware.org Received: from mail.avalus.com (HELO shed.alex.org.uk) (195.177.253.212) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 31 Aug 2006 10:30:53 +0000 Received: from [192.168.100.31] (host-212-18-243-153.static.mailbox.co.uk [212.18.243.153]) by shed.alex.org.uk (Postfix) with ESMTP id 88541C6D46; Thu, 31 Aug 2006 11:30:50 +0100 (BST) Message-ID: <44F6BA49.1000303@alex.org.uk> Date: Thu, 31 Aug 2006 10:30:00 -0000 From: Alex Bligh User-Agent: Thunderbird 1.5.0.5 (X11/20060728) MIME-Version: 1.0 To: Alex Bligh , gdb@sourceware.org Subject: Re: thread_db_get_info: cannot get thread info: generic error on fork()/execvp() References: <20060726214801.14303.qmail@sourceware.org> <20060718124206.30754.qmail@sourceware.org> <20060731130001.GA1823@nevyn.them.org> <44DF8D67.8090502@alex.org.uk> <44F5BCAB.7050400@alex.org.uk> <20060830181439.GA29333@nevyn.them.org> In-Reply-To: <20060830181439.GA29333@nevyn.them.org> Cc: Alex Bligh Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-08/txt/msg00268.txt.bz2 Daniel, Daniel Jacobowitz wrote: > On Wed, Aug 30, 2006 at 05:28:27PM +0100, Alex Bligh wrote: >> Hi, >> >> Now we have a pretty trivial test case to reproduce this problem, >> as per the 20 line program at the bottom of bug 2149, >> is there any chance at all of getting a fix? I currently >> can't debug my app at all because it suffers from this >> problem. I am willing to help in any way I can to debug >> this or test. > > Well, I can reproduce the problem. I can see roughly what's wrong, > too. We still think we're attached to the old thread. > > Could you try this patch? Yep. That fixes it, both on the test case, and on the real program. I can now debug again. Woohoo! Thanks. What's the chance of applying that in RCS and (ideally) providing that and the previous thread fix so debugging as a backport to the Ubuntu Dapper gdb. Alex