This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
RE: [13/15] Address printing
- From: "Pierre Muller" <muller at ics dot u-strasbg dot fr>
- To: "'Ulrich Weigand'" <uweigand at de dot ibm dot com>
- Cc: <gdb-patches at sourceware dot org>
- Date: Fri, 3 Jul 2009 13:57:49 +0200
- Subject: RE: [13/15] Address printing
- References: <200906091521.n59FLL6U002324@d12av02.megacenter.de.ibm.com> from "Ulrich Weigand" at Jun 09, 2009 05:21:21 PM <200907021722.n62HMeVp011168@d12av02.megacenter.de.ibm.com>
Hi all,
it seems to me that
paddress has a noticeably different behavior from
removed paddr function:
paddr was always of the size of 2*ptr_size
and had no leading '0x' while paddress
doesn't have a fixed length and has a leading '0x'.
I was wondering if there are no testsuite failures
related to that change.
core_addr_to_string seems also not to display
addresses with the size of the current target:
it uses sizeof (CORE_ADDR) which might be different
from the size of the current target especially for
--enable-targets=all.
I saw that you used phex (addr, addr_size)
at several places, wouldn't be better to
use target_gdbarch pointer size if target_gdbarch
is valid and fall back to sizeof (CORE_ADDR) only
if current target is not set or if the pointer size
is not set?
Pierre Muller
Pascal language support maintainer for GDB