This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
[RFC] Re: Proposed fix to gdb for printing 64-bit addresses
- From: Michal Ludvig <mludvig at suse dot cz>
- To: Brian Taylor <briant at model dot com>
- Cc: gdb-patches at sources dot redhat dot com, Andrew Cagney <ac131313 at redhat dot com>
- Date: Tue, 07 May 2002 15:19:02 +0200
- Subject: [RFC] Re: Proposed fix to gdb for printing 64-bit addresses
- Organization: SuSE CR
- References: <3CCD8E01.2020500@model.com>
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?
Michal Ludvig
--
* SuSE CR, s.r.o * mludvig@suse.cz
* +420 2 9654 5373 * http://www.suse.cz
Brian Taylor wrote:
> Problem:
> 64-bit addresses reported by 'info break' and 'backtrace' are truncated
> when debugging a 64-bit executable on AIX 4.3.
>
> ChangeLog entry:
> 2002-04-29 Brian Taylor <briant@model.com>
>
> * ui-out.c (ui_out_field_core_addr): Use the function
> 'longest_local_hex_string_custom' to format addresses > 32 bits
> wide.
>