public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ssbssa at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/15684] info mem command for 32 bits host/64 bits target truncates addresses
Date: Sun, 31 Dec 2023 16:26:48 +0000	[thread overview]
Message-ID: <bug-15684-4717-4tJfTDz2Bu@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15684-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=15684

Hannes Domani <ssbssa at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
                 CC|                            |ssbssa at sourceware dot org
   Target Milestone|---                         |7.9
             Status|NEW                         |RESOLVED

--- Comment #2 from Hannes Domani <ssbssa at sourceware dot org> ---
(In reply to Sourceware Commits from comment #1)
> This is an automated email from the git hooks/post-receive script. It was
> generated because a ref change was pushed to the repository containing
> the project "gdb and binutils".
> 
> The branch, master has been updated
>        via  aacd3e8c4f5ac00f1ee41c082c2f10eb7457d04c (commit)
>       from  184d64776bc16fcba7b00e5784e27f52854cc8dd (commit)
> 
> Those revisions listed above that are new to this repository have
> not appeared on any other notification email; so we list those
> revisions in full, below.
> 
> - Log -----------------------------------------------------------------
> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;
> h=aacd3e8c4f5ac00f1ee41c082c2f10eb7457d04c
> 
> commit aacd3e8c4f5ac00f1ee41c082c2f10eb7457d04c
> Author: Catalin Udma <catalin.udma@freescale.com>
> Date:   Mon Dec 15 16:41:29 2014 +0200
> 
>     Fix info mem command for 32 bits host/64 bits target
>     
>     When running gdb on 32 bits host for 64 bits target, info mem command
>     truncates the target address to 32 bits, like in the example below
>     	(gdb) set architecture powerpc:common64
>     	(gdb) mem 0x100000000 0x200000000 rw
>     	(gdb) info mem
>     	1   y  	0x0000000000000000 0x0000000000000000 rw nocache
>     
>     gdb/ChangeLog:
>     
>             PR gdb/15684
>             * memattr.c (mem_info_command): Remove "unsigned long" casts.
>     
>     Signed-off-by: Catalin Udma <catalin.udma@freescale.com>
> 
> -----------------------------------------------------------------------
> 
> Summary of changes:
>  gdb/ChangeLog |    5 +++++
>  gdb/memattr.c |    8 ++++----
>  2 files changed, 9 insertions(+), 4 deletions(-)

Was fixed with this commit.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2023-12-31 16:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-26 16:39 [Bug gdb/15684] New: " ktlnu at yahoo dot com
2014-12-15 14:52 ` [Bug gdb/15684] " cvs-commit at gcc dot gnu.org
2023-12-31 16:26 ` ssbssa at sourceware dot org [this message]

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=bug-15684-4717-4tJfTDz2Bu@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).