From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5465 invoked by alias); 19 May 2005 01:01:46 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 5334 invoked from network); 19 May 2005 01:01:34 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 19 May 2005 01:01:34 -0000 Received: from drow by nevyn.them.org with local (Exim 4.50) id 1DYZPp-0007HN-Dq; Wed, 18 May 2005 21:01:33 -0400 Date: Thu, 19 May 2005 01:01:00 -0000 From: Daniel Jacobowitz To: David Antliff Cc: gdb@sources.redhat.com Subject: Re: remote debugging symbol problem Message-ID: <20050519010133.GB27885@nevyn.them.org> Mail-Followup-To: David Antliff , gdb@sources.redhat.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i X-SW-Source: 2005-05/txt/msg00181.txt.bz2 On Thu, May 19, 2005 at 12:26:33PM +1200, David Antliff wrote: > > Hello, > > We use gdb-6.0 and a PowerPC port of gdbserver to remotely debug our > target application on it's PowerPC platform. Our application forks several > (20 or so) child processes shortly after starting up, and a few of these > child processes create threads. > > Until quite recently, this has all worked fine. I was able to invoke: > > # gdbserver 0.0.0.0:2345 --attach for any of the child processes, > and then run on my development host (x86 linux): > > $ cd > $ gdb > > I am 100% sure the same application binary is running on the host as on > the target (I'm using NFS). > > Normally, once GDB is pointed at the target, the process is interrupted > and GDB can show a stack trace at the point of interruption. > > However, now, I just get this: > > (gdb) target remote 10.16.10.237:2345 > Remote debugging using 10.16.10.237:2345 > 0x0fe896a0 in ?? () > warning: Unable to find dynamic linker breakpoint function. > GDB will be unable to debug shared library initializers > and track explicitly loaded dynamic code. > > My understanding is that the warning is simply because the standard > libraries aren't compiled with GDB support. This used to happen even when > it worked so I'm not concerned about it (should I be?). You should be. This means that GDB has not found your target libraries. Is solib-absolute-prefix set in your cross GDB? -- Daniel Jacobowitz CodeSourcery, LLC