From: Mark Kettenis <kettenis@chello.nl>
To: ac131313@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch rfc rfa:i386] Add i386 specific register groups
Date: Fri, 08 Nov 2002 12:56:00 -0000 [thread overview]
Message-ID: <200211082056.gA8Kudmd024760@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <3DCC1F54.1000108@redhat.com> (message from Andrew Cagney on Fri, 08 Nov 2002 15:32:20 -0500)
Date: Fri, 08 Nov 2002 15:32:20 -0500
From: Andrew Cagney <ac131313@redhat.com>
> Yeah! And you can always say "print $orig_eax", can't you?
(er, quickly checking ...)
(top-gdb) print $orig_eax
$1 = -1
(top-gdb) maint print raw-registers
...
orig_eax 41 41 308 4 int 0xffffffff
Yep, of course you can.
What about save/restore? Should it be saved/restored across an inferior
function call?
Yes it should, so save/restore is OK.
> Hmm, why are all registers in group "general"?
Preserving existing behavior? :-^
Not quite I think. Existing behaviour is for "info registers" to
print everything except st0...st7 and xmm0...xmm7. So it doesn't
print float and vector registers. However it does print the
floating-point control registers and mxcsr which is the SSE control
register. Now that doesn't make any sense to me. Therefore I'd like
"info registers" to print only the general-purpose registers, that is
everything up to and including gs, but nothing else.
(general corresponds to `info all-registers')?
Nope it doesn't. It's "all" that corresponds to "info all-registers",
and "general" that corresponds to "info registers". So I'd want:
if (group == general_reggroup)
return (!fp_regnum_p && !mmx_regnum_p && !sse_regnum_p);
Mark
next prev parent reply other threads:[~2002-11-08 20:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-08 9:53 Andrew Cagney
2002-11-08 12:21 ` Mark Kettenis
2002-11-08 12:32 ` Andrew Cagney
2002-11-08 12:34 ` Daniel Jacobowitz
2002-11-08 12:43 ` Andrew Cagney
2002-11-08 12:51 ` Daniel Jacobowitz
2002-11-08 12:56 ` Mark Kettenis [this message]
2002-11-08 15:09 ` Andrew Cagney
2002-11-08 15:14 ` Mark Kettenis
2002-11-08 16:00 ` Andrew Cagney
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=200211082056.gA8Kudmd024760@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=ac131313@redhat.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