This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: gdb 7.6: Fix info mem command for 32 bits host/64 bits target
- From: Pedro Alves <palves at redhat dot com>
- To: Udma Catalin-Dan-B32721 <B32721 at freescale dot com>
- Cc: "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Wed, 26 Jun 2013 17:06:05 +0100
- Subject: Re: gdb 7.6: Fix info mem command for 32 bits host/64 bits target
- References: <FE751157F0442848A159F3AB4CB1F55B3D9FE8 at 039-SN1MPN1-001 dot 039d dot mgd dot msft dot net>
On 06/26/2013 04:07 PM, Udma Catalin-Dan-B32721 wrote:
> Hi,
> I found an issue with the "info mem" command when running gdb on 32 bits host for 64 bits target architecture.
> "info mem" command truncates the target address to 32 bits, like in the example below:
>
> (gdb) set architecture powerpc:common64
> The target architecture is assumed to be powerpc:common64
> (gdb) mem 0x100000000 0x200000000 rw
> (gdb) info mem
> Using user-defined memory regions.
> Num Enb Low Addr High Addr Attrs
> 1 y 0x0000000000000000 0x0000000000000000 rw nocache
>
> Please find below the proposed patch. Please let me know your comments.
Thanks! The (LONGEST) casts look unnecessary, as
hex_string_custom already takes LONGEST.
This needs a ChangeLog entry. See
<http://sourceware.org/gdb/wiki/ContributionChecklist>. Could
you send one?
In order to backport to the 7.6 branch, we'll need a bugzilla entry
filed, reporting the bug. Could you do that? That will be used
to record the bug fix in <http://sourceware.org/gdb/wiki/GDB_7.6_Release>.
--
Pedro Alves