From: Mark Kettenis <kettenis@chello.nl>
To: ac131313@redhat.com
Cc: drow@mvista.com, colins@google.com, gdb-patches@sources.redhat.com
Subject: Re: patch for printing 64-bit values in i386 registers; STABS format
Date: Mon, 28 Apr 2003 15:22:00 -0000 [thread overview]
Message-ID: <200304272203.h3RM35Ur016419@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <3EA9FDDF.8070205@redhat.com> (message from Andrew Cagney on Fri, 25 Apr 2003 23:32:47 -0400)
Date: Fri, 25 Apr 2003 23:32:47 -0400
From: Andrew Cagney <ac131313@redhat.com>
> I'm afraid I don't understand, and I still don't see your reasoning
> against this approach.
It isn't necessary, just like register convertible and register
raw/virtual size; .... that go before it, also were not necessary. And
now all these years later, GDB is still yet to expunge.
I still don't see how you can get rid of the register convertible
stuff. On the i386 I still need it for variables stuffed into the
floating point registers.
Until someone does the right think - add support for values scattered
across registers and memory - hacks should be confined to architecture
specific code.
But even if someone does add support for values scattered across
multiple registers and/or memory, we still need the architecture
method I proposed. There simply is too much debugging info out there
that can't express values being scattered across multiple registers.
And I don't think the hack you proposed is a good idea. I think it's
better to add a new architecture method with a clear purpose than
abuse an existing mechanism for something that it wasn't quite
intended for. Even if the architecture method in question would only
be used by a single target.
Mark
next prev parent reply other threads:[~2003-04-27 22:03 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 [this message]
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
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=200304272203.h3RM35Ur016419@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=ac131313@redhat.com \
--cc=colins@google.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