From: Daniel Jacobowitz <drow@false.org>
To: Victor STINNER <victor.stinner@haypocalc.com>
Cc: gdb@sources.redhat.com
Subject: Re: Display libc function names instead of address ?
Date: Thu, 16 Jun 2005 04:43:00 -0000 [thread overview]
Message-ID: <20050616044313.GA5950@nevyn.them.org> (raw)
In-Reply-To: <1118892960.12713.5.camel@haypopc>
On Thu, Jun 16, 2005 at 05:36:00AM +0200, Victor STINNER wrote:
> Hi,
>
> I woud like to know if it is possible to display libc functions name
> instead of their address. Example :
>
> (1) (...) // prepare parameters
> call 0x8048728
>
> (2) jmp *0x804a6b0 // in relocation table, at 0x08048728
>
> And if I do a "objdump -R file | grep 0x804a6b0", it answers printf. So
> is it possible to display "call printf" instead of "call 0x8048728" ? Or
> at least display "jmp *<printf>" instead of "jmp *0x804a6b0" ?
>
> I think that gdb can already read relocation table because "print
> printf" command give me the function address.
>
> I hope that it's just an option :-)
GDB can't do this - but, I think, that the very latest BFD/opcodes
library supports this for some targets. Someone needs to hook those
bits up to GDB.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-06-16 4:43 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 [this message]
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
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=20050616044313.GA5950@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=victor.stinner@haypocalc.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