Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Why does ui_out_field_core_addr pad with leading zeroes?
Date: Thu, 18 Mar 2010 18:23:00 -0000	[thread overview]
Message-ID: <e394668d1003181123m5347420am335bb97775a1a782@mail.gmail.com> (raw)
In-Reply-To: <201003181747.29518.pedro@codesourcery.com>

On Thu, Mar 18, 2010 at 10:47 AM, Pedro Alves <pedro@codesourcery.com> wrote:
> On Thursday 18 March 2010 17:30:15, Doug Evans wrote:
>> I couldn't find an explanation of why ui_out_field_core_addr pads
>> the address with leading zeroes.
>>
>> Does anyone know?
>
> Personally, I find that zeros on the left serve as
> a hint at the largest possible address width in
> the architecture.  That'd be my educated guess.

There are other ways to find that without sacrificing readability.

> It also aids visual alignment I suppose.  Try also adding
> a breakpoint in a shared library in your example,
> and redoing `info break'. The column is presently
> aligned left.  I suspect it won't look as neat after
> your patch.

I realize that *could* happen, but since we're doing this fancy ui-out
thing, I would expect it's the job of the front end to do any desired
alignment.

For reference sake, this is what I get with my patch:

(gdb) b main
Breakpoint 2 at 0x40049c: file hello.c, line 6.
(gdb) i b
Num     Type           Disp Enb Address            What
2       breakpoint     keep y   0x40049c           in main at hello.c:6
(gdb) b printf
Breakpoint 3 at 0x7ffff7acbe40
(gdb) i b
Num     Type           Disp Enb Address            What
2       breakpoint     keep y   0x40049c           in main at hello.c:6
3       breakpoint     keep y   0x7ffff7acbe40     <printf>
(gdb)


  reply	other threads:[~2010-03-18 18:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-18 17:30 Doug Evans
2010-03-18 17:47 ` Pedro Alves
2010-03-18 18:23   ` Doug Evans [this message]
2010-03-18 18:58     ` Mark Kettenis
2010-03-18 19:19       ` Doug Evans
2010-03-18 19:25         ` Jan Kratochvil
2010-03-18 19:38           ` Doug Evans
2010-03-18 19:47             ` Pedro Alves
2010-03-18 20:49               ` Doug Evans
2010-03-18 19:51             ` Daniel Jacobowitz
2010-03-18 19:56               ` Pedro Alves
2010-03-18 20:03               ` Mark Kettenis
2010-03-18 20:59               ` Doug Evans
2010-03-18 17:52 ` Joel Brobecker
2010-03-18 18:52 ` Mark Kettenis

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=e394668d1003181123m5347420am335bb97775a1a782@mail.gmail.com \
    --to=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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