This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: remote debugging symbol problem
- From: Daniel Jacobowitz <drow at false dot org>
- To: David Antliff <dave dot antliff at paradise dot net dot nz>
- Cc: gdb at sources dot redhat dot com
- Date: Wed, 18 May 2005 21:01:33 -0400
- Subject: Re: remote debugging symbol problem
- References: <Pine.LNX.4.61.0505191210040.25332@localhost>
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 <pid> for any of the child processes,
> and then run on my development host (x86 linux):
>
> $ cd <application-src-dir>
> $ gdb <application-binary>
>
> 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