Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch rfc rfa:i386] Add i386 specific register groups
Date: Fri, 08 Nov 2002 12:32:00 -0000	[thread overview]
Message-ID: <3DCC1F54.1000108@redhat.com> (raw)
In-Reply-To: <86wunn6cea.fsf@elgar.kettenis.dyndns.org>

> Andrew Cagney <ac131313@redhat.com> writes:
> 
> 
>> I should note that the orig_eax register is only a member of the system, 
>> save and restore reggroups, and hence is no longer displayed by either 
>> `info registers' or `info all-registers'.  If you're really desperate 
>> you can use the `maint print raw-registers` (which is in the manual :-)
> 
> 
> 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?

>> This ok?
> 
> 
> Hmm, why are all registers in group "general"?

Preserving existing behavior? :-^

 > I'd expect the group
> general to only include the general-purpose registers.

So you'd like the mmx and sse registers excluded
(general corresponds to `info all-registers')?

Just give the word,

Andrew



  reply	other threads:[~2002-11-08 20:32 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 [this message]
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
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=3DCC1F54.1000108@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@chello.nl \
    /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