From: Eli Zaretskii <eliz@gnu.org>
To: Victor STINNER <victor.stinner@haypocalc.com>
Cc: gdb-patches@sources.redhat.com, ezannoni@redhat.com
Subject: Re: Display libc function names instead of address ?
Date: Thu, 16 Jun 2005 18:46:00 -0000 [thread overview]
Message-ID: <uy89a13yo.fsf@gnu.org> (raw)
In-Reply-To: <20050616162605.GA32580@nevyn.them.org> (message from Daniel Jacobowitz on Thu, 16 Jun 2005 12:26:05 -0400)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]
> Date: Thu, 16 Jun 2005 12:26:05 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: gdb-patches@sources.redhat.com
>
> On Thu, Jun 16, 2005 at 05:45:59PM +0200, Victor STINNER wrote:
> > Le jeudi 16 juin 2005 à 11:19 -0400, Daniel Jacobowitz a écrit :
> > > Thanks for checking! That's output from objdump, right? It doesn't
> > > seem to work for me in GDB, just in objdump. But perhaps I can figure
> > > out where to wire it in.
> >
> > Yep, it's in objdump. I think that you just have to update bfd and
> > opcodes libraries, no ?
>
> No - GDB also needs a change.
>
> This has been on my todo list for months, ever since objdump gained
> support. Here's an implementation - the patch applies to GDB CVS.
> Elena, is this patch OK?
>
> Tested on i686-pc-linux-gnu. It leaves a stray if (1) to minimize the
> size of the diff; I would remove that as an obvious followup.
Will this change modify what GDB displays in response to some command?
If so, please see whether something in the manual needs a suitable
change as well.
TIA
next prev parent reply other threads:[~2005-06-16 18:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1118892960.12713.5.camel@haypopc>
[not found] ` <20050616044313.GA5950@nevyn.them.org>
[not found] ` <1118934045.2827.4.camel@haypopc>
[not found] ` <20050616151934.GA11296@nevyn.them.org>
[not found] ` <1118936759.24041.23.camel@haypopc>
2005-06-16 16:26 ` Daniel Jacobowitz
2005-06-16 18:46 ` Eli Zaretskii [this message]
2005-06-16 18:49 ` Daniel Jacobowitz
2005-09-18 1:45 ` Daniel Jacobowitz
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=uy89a13yo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@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