This is the mail archive of the
mailing list for the GDB project.
Re: warning: Unable to find dynamic linker breakpoint function
- From: Daniel Jacobowitz <drow at false dot org>
- To: Adam Richard <g4c9z at unb dot ca>
- Cc: gdb at sources dot redhat dot com
- Date: Tue, 4 Jan 2005 18:06:44 -0500
- Subject: Re: warning: Unable to find dynamic linker breakpoint function
- References: <email@example.com> <20041229214406.GA5135@nevyn.them.org> <firstname.lastname@example.org> <20041231004046.GA17098@nevyn.them.org> <email@example.com> <20041231190856.GA10862@nevyn.them.org> <firstname.lastname@example.org>
On Tue, Jan 04, 2005 at 07:03:19PM -0400, Adam Richard wrote:
> Quoting Daniel Jacobowitz <email@example.com>:
> > On Fri, Dec 31, 2004 at 09:51:22AM -0400, Adam Richard wrote:
> > > > > I read somewhere that it
> > > > might
> > > > > have to do with a stripped gdb but I don't understand why I can't have a
> > stripped
> > > > gdb
> > > > > so I'm hoping for an explanation.
> > > >
> > > > Not a stripped GDB, a stripped dynamic linker (/lib/ld-linux.so.2).
> > >
> > > OK, why does a stripped dynamic linker impair debugging? I noticed that that file
> > is
> > > part of the glibc package, and I can see why stripping it would prevent being able
> > to
> > > step into its functions for any program which depends on it (which is most
> > programs).
> > > But I still don't understand your explanation.
> > Because GDB has trouble finding the list of available shared libraries.
> I tried recompiling glibc without stripping it (at least I used the "nostrip" option in
> Gentoo) and it didn't make a difference. Are you sure that's what makes the warning go
You'll have to debug GDB yourself to figure out why it's being