From: Pedro Alves <palves@redhat.com>
To: Udma Catalin-Dan-B32721 <B32721@freescale.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: gdb 7.6: Fix info mem command for 32 bits host/64 bits target
Date: Wed, 26 Jun 2013 16:07:00 -0000 [thread overview]
Message-ID: <51CB116D.7060009@redhat.com> (raw)
In-Reply-To: <FE751157F0442848A159F3AB4CB1F55B3D9FE8@039-SN1MPN1-001.039d.mgd.msft.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
next prev parent reply other threads:[~2013-06-26 16:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 15:10 Udma Catalin-Dan-B32721
2013-06-26 16:07 ` Pedro Alves [this message]
2013-06-26 16:11 ` Pedro Alves
2013-06-26 16:17 ` Pedro Alves
2013-06-26 17:11 ` Tom Tromey
2013-06-26 16:20 ` Udma Catalin-Dan-B32721
2013-06-27 8:42 ` Udma Catalin-Dan-B32721
2013-06-27 8:44 ` Pedro Alves
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=51CB116D.7060009@redhat.com \
--to=palves@redhat.com \
--cc=B32721@freescale.com \
--cc=gdb-patches@sourceware.org \
/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