From: Daniel Jacobowitz <drow@false.org>
To: Adam Richard <g4c9z@unb.ca>
Cc: gdb@sources.redhat.com
Subject: Re: warning: Unable to find dynamic linker breakpoint function
Date: Fri, 31 Dec 2004 19:09:00 -0000 [thread overview]
Message-ID: <20041231190856.GA10862@nevyn.them.org> (raw)
In-Reply-To: <1104501082.41d5595a81666@webmail.unb.ca>
On Fri, Dec 31, 2004 at 09:51:22AM -0400, Adam Richard wrote:
> That doesn't really make sense to me. Setting a breakpoint *is* a debugging task. Why
> does it need to set a breakpoint in order to debug?
So that it knows what shared libraries are loaded in the program you're
debugging. It hits the breakpoint when the list changes.
> > > Linux, kernel 2.6.9, on an AMD Athlon XP processor. 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.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-12-31 19:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-29 21:33 Adam Richard
2004-12-29 21:44 ` Daniel Jacobowitz
2004-12-31 0:36 ` Adam Richard
2004-12-31 0:41 ` Daniel Jacobowitz
2004-12-31 13:51 ` Adam Richard
2004-12-31 19:09 ` Daniel Jacobowitz [this message]
2005-01-04 23:04 ` Adam Richard
2005-01-04 23:07 ` Daniel Jacobowitz
2005-01-05 3:10 ` Adam Richard
2005-03-11 21:42 Manoj Iyer
2005-03-12 0:14 ` Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041231190856.GA10862@nevyn.them.org \
--to=drow@false.org \
--cc=g4c9z@unb.ca \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox