From: Mark Kettenis <kettenis@chello.nl>
To: ac131313@redhat.com
Cc: drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: patch for printing 64-bit values in i386 registers; STABS format
Date: Mon, 28 Apr 2003 00:51:00 -0000 [thread overview]
Message-ID: <200304272044.h3RKivcZ000307@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <3EA9B6AE.90001@redhat.com> (message from Andrew Cagney on Fri, 25 Apr 2003 18:29:02 -0400)
Date: Fri, 25 Apr 2003 18:29:02 -0400
From: Andrew Cagney <ac131313@redhat.com>
User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223
X-Accept-Language: en-us, en
Cc: Mark Kettenis <kettenis@chello.nl>, colins@google.com,
gdb-patches@sources.redhat.com
Content-Type: text/plain; charset=us-ascii; format=flowed
> On Fri, Apr 25, 2003 at 11:21:13PM +0200, Mark Kettenis wrote:
>
>> Date: Thu, 24 Apr 2003 20:27:44 -0400
>> From: Daniel Jacobowitz <drow@mvista.com>
>>
>> Hey, Mark, this sounds very much like a change you proposed. What ever
>> happened to that patch?
>>
>> It's still happily sitting in my tree :-(. There didn't seem to be
>> any consensus on whether making this change was a good idea. I still
>> think it is. It's an improvement for the majority of our users, and
>> it isn't making things worse for others. Do you think I should
>> re-submit my patch?
>
>
> I do, definitely.
FYI,
It's possible to fix this without adding an architecture method, or
implementing location expressions (the penny just dropped). The basic
problem is the same as for the MIPS - need a custom register area. Hence:
- define a sequence of nameless cooked ([NUM_REGS ..
NUM_REGS+NUM_PSEUDO_REGS) range) registers ordered the way stabs would
like them
- modify the existing stabs_regnum_to_regnum to map the messed up
registers onto those values
Ugh, Yuck! Yes it works, but isn't this a terrible hack? Oh and
using nameless cooked registers means that
info address variable
no longer prints the right thing if variable lives in a register.
Mark
next prev parent reply other threads:[~2003-04-27 20:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-25 0:27 Colin Smith
2003-04-25 2:07 ` Daniel Jacobowitz
2003-04-25 22:18 ` Mark Kettenis
2003-04-25 22:24 ` Daniel Jacobowitz
2003-04-26 3:05 ` Andrew Cagney
2003-04-26 3:20 ` Daniel Jacobowitz
2003-04-26 3:32 ` Andrew Cagney
2003-04-26 3:39 ` Daniel Jacobowitz
2003-04-26 8:25 ` Andrew Cagney
2003-04-27 3:47 ` Daniel Jacobowitz
2003-04-28 15:22 ` Mark Kettenis
2003-04-28 16:09 ` Andrew Cagney
2003-04-28 16:14 ` Daniel Jacobowitz
2003-04-28 16:15 ` Andrew Cagney
2003-04-28 16:37 ` Daniel Jacobowitz
2003-04-28 19:26 ` Andrew Cagney
2003-04-28 22:47 ` Daniel Jacobowitz
2003-04-29 2:15 ` re-ordered i386 regcache Andrew Cagney
2003-04-29 4:45 ` Daniel Jacobowitz
2003-04-29 14:30 ` Andrew Cagney
2003-04-29 15:08 ` Daniel Jacobowitz
2003-04-29 15:25 ` Andrew Cagney
2003-04-30 3:37 ` Daniel Jacobowitz
2003-04-30 14:28 ` Andrew Cagney
2003-04-30 18:20 ` Daniel Jacobowitz
2003-04-28 20:06 ` Re: patch for printing 64-bit values in i386 registers; STABS format Colin Smith
2003-04-28 0:51 ` Mark Kettenis [this message]
2003-04-28 16:18 ` Andrew Cagney
2003-04-28 17:30 ` Daniel Jacobowitz
2003-04-25 0:29 Colin Smith
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=200304272044.h3RKivcZ000307@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.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