This is the mail archive of the
gdb@sources.redhat.com
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 19:03:19 -0400
- Subject: Re: warning: Unable to find dynamic linker breakpoint function
- References: <1104355984.41d322909c42d@webmail.unb.ca> <20041229214406.GA5135@nevyn.them.org> <1104453359.41d49eef5093e@webmail.unb.ca> <20041231004046.GA17098@nevyn.them.org> <1104501082.41d5595a81666@webmail.unb.ca> <20041231190856.GA10862@nevyn.them.org>
Quoting Daniel Jacobowitz <drow@false.org>:
> 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
away?