From: Doug Evans <dje@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
pedro@codesourcery.com, gdb-patches@sourceware.org
Subject: Re: [RFC] Why does ui_out_field_core_addr pad with leading zeroes?
Date: Thu, 18 Mar 2010 19:38:00 -0000 [thread overview]
Message-ID: <e394668d1003181238p1ccf89b0s682db8cbe1c7fd10@mail.gmail.com> (raw)
In-Reply-To: <20100318192535.GA25322@host0.dyn.jankratochvil.net>
On Thu, Mar 18, 2010 at 12:25 PM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> On Thu, 18 Mar 2010 20:19:11 +0100, Doug Evans wrote:
>> Having stared at both alignments, I don't see aligning the address to
>> the right as being easier to read than aligning them to the left, and
>> even less so.
>>
>> Right Aligned
>>
>> (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)
>>
>> Left Aligned
>>
>> (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)
>
> I am definitely for the "Right Aligned" one and against the "Left Aligned"
> one. While analyzing various crash dumps one looks for the same last three
> digits (ignoring PIC/PIE different PAGE_SIZE-aligned placement). Also
> sometimes sorting addresses from various sources by hand to find out the
> memory layout and having to additionally re-align even the GDB dump itself is
> not helpful.
[It seemed like ui-out should make this easy, and voila.]
2010-03-18 Doug Evans <dje@google.com>
* ui-out.c (ui_out_field_core_addr): Don't pad address with leading
zeroes.
* breakpoint.c (breakpoint_1): Right align breakpoint addresses.
Index: ui-out.c
===================================================================
RCS file: /cvs/src/src/gdb/ui-out.c,v
retrieving revision 1.45
diff -u -p -r1.45 ui-out.c
--- ui-out.c 12 Jan 2010 21:40:24 -0000 1.45
+++ ui-out.c 18 Mar 2010 17:19:07 -0000
@@ -498,12 +498,8 @@ ui_out_field_core_addr (struct ui_out *u
address &= ((CORE_ADDR) 1 << addr_bit) - 1;
/* FIXME: cagney/2002-05-03: Need local_address_string() function
- that returns the language localized string formatted to a width
- based on gdbarch_addr_bit. */
- if (addr_bit <= 32)
- strcpy (addstr, hex_string_custom (address, 8));
- else
- strcpy (addstr, hex_string_custom (address, 16));
+ that returns the language localized string. */
+ strcpy (addstr, hex_string (address));
ui_out_field_string (uiout, fldname, addstr);
}
Index: breakpoint.c
===================================================================
RCS file: /cvs/src/src/gdb/breakpoint.c,v
retrieving revision 1.462
diff -u -p -r1.462 breakpoint.c
--- breakpoint.c 16 Mar 2010 08:42:20 -0000 1.462
+++ breakpoint.c 18 Mar 2010 19:35:08 -0000
@@ -4743,9 +4743,9 @@ breakpoint_1 (int bnum, int allflag)
if (nr_printable_breakpoints > 0)
annotate_field (4);
if (print_address_bits <= 32)
- ui_out_table_header (uiout, 10, ui_left, "addr", "Address");/* 5 */
+ ui_out_table_header (uiout, 10, ui_right, "addr", "Address");/* 5 */
else
- ui_out_table_header (uiout, 18, ui_left, "addr", "Address");/* 5 */
+ ui_out_table_header (uiout, 18, ui_right, "addr", "Address");/* 5 */
}
if (nr_printable_breakpoints > 0)
annotate_field (5);
next prev parent reply other threads:[~2010-03-18 19:38 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
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 [this message]
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=e394668d1003181238p1ccf89b0s682db8cbe1c7fd10@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=mark.kettenis@xs4all.nl \
--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