From: Daniel Jacobowitz <drow@mvista.com>
To: Michal Ludvig <mludvig@suse.cz>
Cc: Brian Taylor <briant@model.com>,
gdb-patches@sources.redhat.com,
Andrew Cagney <ac131313@redhat.com>
Subject: Re: [RFC] Re: Proposed fix to gdb for printing 64-bit addresses
Date: Tue, 07 May 2002 07:56:00 -0000 [thread overview]
Message-ID: <20020507145558.GB17670@nevyn.them.org> (raw)
In-Reply-To: <3CD7D446.5020800@suse.cz>
On Tue, May 07, 2002 at 03:19:02PM +0200, Michal Ludvig wrote:
> Hi,
> unfortunately this produces quite ugly output on x86-64 where the
> debugged code usually lives on low addresses and thus the PC is
> prepended with a long string of zeros. Now:
> #0 0x00000000004000d3 in cpyptrs () at dwarf.c:11
> #1 0x00000000004000f8 in func () at dwarf.c:19
>
> I propose to change the format string from "016l" to just "l" so that
> only valid digits will be printed:
> #0 0x4000d3 in cpyptrs () at dwarf.c:11
> #1 0x4000f8 in func () at dwarf.c:19
>
> Than there is no need for different handling of 32/64b archs.
>
> Comments?
I'd rather not do that, actually; I find it very confusing when a
seven-digit hex number is printed (I assume it is an eight-digit one).
It might be appropriate to print just eight digits of low 64-bit
addresses... I don't feel too strongly about this issue, though.
Anyone else have an opinion?
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-05-07 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-29 11:16 Proposed fix to gdb for printing 64-bit addresses on AIX Brian Taylor
2002-05-04 20:08 ` Andrew Cagney
2002-05-07 6:19 ` [RFC] Re: Proposed fix to gdb for printing 64-bit addresses Michal Ludvig
2002-05-07 7:56 ` Daniel Jacobowitz [this message]
2002-05-07 8:54 ` Michal Ludvig
2002-05-07 10:49 ` Andrew Cagney
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=20020507145558.GB17670@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=briant@model.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mludvig@suse.cz \
/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