From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2381 invoked by alias); 5 Nov 2005 02:59:06 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 2352 invoked by uid 22791); 5 Nov 2005 02:59:01 -0000 Received: from ausmtp02.au.ibm.com (HELO ausmtp02.au.ibm.com) (202.81.18.187) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sat, 05 Nov 2005 02:59:01 +0000 Received: from sd0208e0.au.ibm.com (d23rh904.au.ibm.com [202.81.18.202]) by ausmtp02.au.ibm.com (8.12.10/8.12.10) with ESMTP id jA52r1GW231988 for ; Sat, 5 Nov 2005 13:53:06 +1100 Received: from d23av01.au.ibm.com (d23av01.au.ibm.com [9.190.250.242]) by sd0208e0.au.ibm.com (8.12.10/NCO/VERS6.7) with ESMTP id jA531rHa179856 for ; Sat, 5 Nov 2005 14:01:54 +1100 Received: from d23av01.au.ibm.com (loopback [127.0.0.1]) by d23av01.au.ibm.com (8.12.11/8.13.3) with ESMTP id jA52wpHc029665 for ; Sat, 5 Nov 2005 13:58:52 +1100 Received: from [9.181.133.252] ([9.181.133.252]) by d23av01.au.ibm.com (8.12.11/8.12.11) with ESMTP id jA52wor0029656; Sat, 5 Nov 2005 13:58:50 +1100 Date: Sat, 05 Nov 2005 02:59:00 -0000 From: Wu Zhou To: Michael Snyder cc: gdb@sources.redhat.com, mysea000@163.com Subject: Re: who can explain the pseudo-registers and its mechanism to me?thanks In-Reply-To: <436BB1E7.10907@redhat.com> Message-ID: References: <436BB1E7.10907@redhat.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2005-11/txt/msg00118.txt.bz2 On Fri, 4 Nov 2005, Michael Snyder wrote: > "ayang" 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 <>? Just my two cents anyway. Regards - Wu Zhou