Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: msnyder@redhat.com, fnf@redhat.com,
	gdb-patches@sources.redhat.com, Richard.Earnshaw@arm.com
Subject: Re: [RFC] "info registers" is misleading
Date: Tue, 22 Jan 2002 05:47:00 -0000	[thread overview]
Message-ID: <200201221347.NAA15786@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Tue, 22 Jan 2002 12:46:18 +0200." <8361-Tue22Jan2002124617+0200-eliz@is.elta.co.il>

> > Date: Mon, 21 Jan 2002 23:08:36 -0800
> > From: Michael Snyder <msnyder@redhat.com>
> > 
> > This is an old old issue.  The frame pointer register
> > is special.  Info registers does not show the actual
> > value of the fp register -- it shows the virtual frame pointer
> > (the address of the function's stack frame).  Usually
> > it's the same value -- unles you're in a frameless function
> > (ie. one that does not use the frame pointer register).
> 
> Shouldn't we document this?  I can write up the change, if you tell
> me that the above description is all that there is to it.

No, we should fix it.  Lying about what is in a machine register is just 
misleading.

R.


  reply	other threads:[~2002-01-22 13:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-21 22:51 Fred Fish
2002-01-21 23:13 ` Michael Snyder
2002-01-22  2:46   ` Eli Zaretskii
2002-01-22  5:47     ` Richard Earnshaw [this message]
2002-01-22  7:23     ` Andrew Cagney
2002-01-22  4:09   ` Richard Earnshaw
2002-01-22  7:49     ` Michael Snyder
2002-01-22  7:21 ` Andrew Cagney
2002-01-22  7:44 Michael Elizabeth Chastain

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=200201221347.NAA15786@cam-mail2.cambridge.arm.com \
    --to=rearnsha@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=eliz@is.elta.co.il \
    --cc=fnf@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@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