From: Daniel Jacobowitz <drow@false.org>
To: gdb@sources.redhat.com
Subject: Re: Display libc function names instead of address ?
Date: Fri, 17 Jun 2005 13:56:00 -0000 [thread overview]
Message-ID: <20050617135630.GA24853@nevyn.them.org> (raw)
In-Reply-To: <uslzh1cvu.fsf@gnu.org>
On Fri, Jun 17, 2005 at 12:44:21PM +0200, Eli Zaretskii wrote:
> > Date: Thu, 16 Jun 2005 15:03:15 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: victor.stinner@haypocalc.com, gdb@sources.redhat.com
> >
> > Yes, Windows is not affected by this problem - it's related to shared
> > libraries and dynamic linking, and Windows DLL linking is different
> > enough that it does not have this quirk - though I'm sure it has plenty
> > of its own.
>
> Ah, the lights go on: so this problem only happens with dynamically
> linked programs? If so, that is what I was missing. Thanks for
> explaining it.
Right! Sorry that wasn't clear. The patch actually affects things
other than dynamic linking - but not for most platforms. It fills in
symbols at places where there are no symbols in the ELF object, but
symbols would be useful to have, and there's a logical symbol to put
there. Another example is PowerPC64 "dot" symbols, which label
function descriptors.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-06-17 13:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-16 3:36 Victor STINNER
2005-06-16 4:43 ` Daniel Jacobowitz
2005-06-16 15:04 ` Victor STINNER
2005-06-16 15:20 ` Daniel Jacobowitz
2005-06-16 15:46 ` Victor STINNER
2005-06-16 18:21 ` Eli Zaretskii
2005-06-16 18:29 ` Daniel Jacobowitz
2005-06-16 18:56 ` Eli Zaretskii
2005-06-16 19:03 ` Daniel Jacobowitz
2005-06-17 9:44 ` Eli Zaretskii
2005-06-17 11:44 ` Victor STINNER
2005-06-17 13:56 ` Daniel Jacobowitz [this message]
2005-06-18 13:12 ` Eli Zaretskii
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=20050617135630.GA24853@nevyn.them.org \
--to=drow@false.org \
--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