From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7567 invoked by alias); 27 Sep 2006 18:11:08 -0000 Received: (qmail 7558 invoked by uid 22791); 27 Sep 2006 18:11:07 -0000 X-Spam-Check-By: sourceware.org Received: from mx2.palmsource.com (HELO mx2.palmsource.com) (12.7.175.14) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 27 Sep 2006 18:11:01 +0000 Received: from localhost (localhost [127.0.0.1]) by localhost.domain.tld (Postfix) with ESMTP id AE23126E47; Wed, 27 Sep 2006 11:10:59 -0700 (PDT) Received: from mx2.palmsource.com ([127.0.0.1]) by localhost (mx2.palmsource.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 17663-04-7; Wed, 27 Sep 2006 11:10:58 -0700 (PDT) Received: from ussunex01.palmsource.com (unknown [192.168.101.9]) by mx2.palmsource.com (Postfix) with ESMTP id D3D3E26E34; Wed, 27 Sep 2006 11:10:58 -0700 (PDT) Received: from 192.168.92.59 ([192.168.92.59]) by ussunex01.palmsource.com ([192.168.101.9]) via Exchange Front-End Server owa.palmsource.com ([10.0.20.17]) with Microsoft Exchange Server HTTP-DAV ; Wed, 27 Sep 2006 18:10:59 +0000 Received: from svmsnyderlnx by owa.palmsource.com; 27 Sep 2006 11:10:58 -0700 Subject: Re: howto debug libthread_db From: Michael Snyder To: carmelo73@gmail.com Cc: Andreas Schwab , gdb@sourceware.org In-Reply-To: <451A18E0.90408@gmail.com> References: <45193401.7000502@gmail.com> <1159294840.24808.76.camel@localhost.localdomain> <451A18E0.90408@gmail.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Wed, 27 Sep 2006 18:11:00 -0000 Message-Id: <1159380658.9768.34.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 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-09/txt/msg00165.txt.bz2 On Wed, 2006-09-27 at 08:23 +0200, Carmelo Amoroso wrote: > Andreas Schwab wrote: > > Michael Snyder writes: > > > >> When you debug gdb with gdb, it is easier if you change the prompt. > >> I usually do this in the 'parent' gdb, so I can tell it apart from > >> the 'child' gdb: > > > > Or just run it from the gdb build directory, which contains a .gdbinit > > that does more useful things. > > > Hi, > my one is a cross build, is it ok copying the .gdbinit from the host > build directory to the target platform ? Won't do any good -- gdbserver does not use that file. It has to be visible to gdb.