This is the mail archive of the
mailing list for the GDB project.
Re: warning: Unable to find dynamic linker breakpoint function
- From: Adam Richard <g4c9z at unb dot ca>
- To: gdb at sources dot redhat dot com
- Cc: Daniel Jacobowitz <drow at false dot org>
- Date: Tue, 4 Jan 2005 23:09:23 -0400
- 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> <20050104230644.GA27358@nevyn.them.org>
> > > > > > 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
> > > is
> > > > part of the glibc package, and I can see why stripping it would prevent being
> > > 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
> > away?
> You'll have to debug GDB yourself to figure out why it's being
> produced, then.
Actually, I just discovered what was wrong. I didn't have debug info compiled into
glibc. After including it (with the debug USE flag in Gentoo; I don't know how to do
it normally), the warning went away.
Thanks for all your help.