From: "Eli Zaretskii" <eliz@gnu.org>
To: gdb@sources.redhat.com
Cc: dave.antliff@paradise.net.nz
Subject: Re: remote debugging symbol problem
Date: Thu, 19 May 2005 04:00:00 -0000 [thread overview]
Message-ID: <01c55c26$Blat.v2.4$f6a75040@zahav.net.il> (raw)
In-Reply-To: <20050519010133.GB27885@nevyn.them.org> (message from Daniel Jacobowitz on Wed, 18 May 2005 21:01:33 -0400)
> Date: Wed, 18 May 2005 21:01:33 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: gdb@sources.redhat.com
>
> > (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.
If this is the cause, shouldn't GDB tell that explicitly? I mean,
it's quite hard, given ``unable to find dynamic linker breakpoint
function'' to figure out that the reason is a failed search for the
libraries, except perhaps for wizards such as Daniel ;-)
Should we teach GDB be more explicit here?
prev parent reply other threads:[~2005-05-19 4:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 0:26 David Antliff
2005-05-19 1:01 ` Daniel Jacobowitz
2005-05-19 3:53 ` David Antliff
2005-05-19 4:00 ` Eli Zaretskii [this message]
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='01c55c26$Blat.v2.4$f6a75040@zahav.net.il' \
--to=eliz@gnu.org \
--cc=dave.antliff@paradise.net.nz \
--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