From: Jim Blandy <jimb@codesourcery.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Michael Snyder <Michael.Snyder@palmsource.com>,
gdb-patches@sourceware.org
Subject: Re: [patch] Cut memory address width
Date: Wed, 27 Sep 2006 20:19:00 -0000 [thread overview]
Message-ID: <m3k63pukmn.fsf@codesourcery.com> (raw)
In-Reply-To: <20060927185544.GA6821@nevyn.them.org> (Daniel Jacobowitz's message of "Wed, 27 Sep 2006 14:55:44 -0400")
Daniel Jacobowitz <drow@false.org> writes:
> On Wed, Sep 27, 2006 at 08:37:16PM +0200, Jan Kratochvil wrote:
>> In such case `paddress' should print full 64-bit addresses.
>> Currently it is weird as it refuses to access memory while it will show you
>> that you were accessing 0xffffce70 - the already cut form - it lies.
>
> Yes, I'm inclined to agree with this. I've encountered it a time or
> two, mostly while working on MIPS64, and it's really bewildering!
> If we have garbage in the high bits, that's a problem already.
>
> I don't know what else would break but unless someone else does, I
> think we should change paddress to print what it's got.
Definitely. Having paddress "fix" things adds insult to injury. :)
next prev parent reply other threads:[~2006-09-27 20:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 16:15 Jan Kratochvil
2006-09-27 18:20 ` Michael Snyder
2006-09-27 18:22 ` Daniel Jacobowitz
2006-09-27 18:37 ` Jan Kratochvil
2006-09-27 18:55 ` Daniel Jacobowitz
2006-09-27 20:19 ` Jim Blandy [this message]
2006-09-27 19:01 ` Mark Kettenis
2006-09-28 17:27 ` Jan Kratochvil
2006-10-05 22:26 ` Daniel Jacobowitz
2006-09-27 19:23 ` Jim Blandy
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=m3k63pukmn.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=Michael.Snyder@palmsource.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
/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