From: Wu Zhou <woodzltc@cn.ibm.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: gdb@sources.redhat.com, mysea000@163.com
Subject: Re: who can explain the pseudo-registers and its mechanism to me?thanks
Date: Sat, 05 Nov 2005 02:59:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.63.0511051058120.25039@linux.site> (raw)
In-Reply-To: <436BB1E7.10907@redhat.com>
On Fri, 4 Nov 2005, Michael Snyder wrote:
> "ayang" <mysea000 at 163 dot com> wrote:
> > hello,
> > I am puzzled by the the pseudo-registers and its mechanism when I >
> read the gdb source.It is not described in gdbint.who can explain the >
> pseudo-registers and its mechanism to me?thanks.
>
> Pseudo-registers are fake registers that do not exist
> (at least as represented) on the target. The basic distinction
> is that gdb fetches the values of "real" registers from the
> target, but computes or composes the values of "pseudo" registers
> locally. An example might be a double-wide pseudo-register
> that is composed from the values of two ordinary registers.
> GDB fetches the values of the two ordinary registers, but
> then combines them to produce the value of the pseudo-register.
>
> If a user changes the value of the pseudo-register, it may
> be necessary for gdb to change the target values from which
> the pseudo-register was composed.
>
Good explanation. At least for me. :-) Maybe this can get into <<GDB
internal>>?
Just my two cents anyway.
Regards
- Wu Zhou
next prev parent reply other threads:[~2005-11-05 2:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 19:09 Michael Snyder
2005-11-05 2:59 ` Wu Zhou [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-03 9:16 ayang
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=Pine.LNX.4.63.0511051058120.25039@linux.site \
--to=woodzltc@cn.ibm.com \
--cc=gdb@sources.redhat.com \
--cc=msnyder@redhat.com \
--cc=mysea000@163.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).