Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: "Theodore A. Roth" <troth@openavr.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC:avr] use regcache instead of read_register
Date: Fri, 20 Jun 2003 17:39:00 -0000	[thread overview]
Message-ID: <3EF34557.4090209@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0306201003210.9653@knuth.amplepower.com>


> I guess a similar change to d10v_read_pc.
> 
> Just noticed that the d10v seems to use d10v_unwind_sp instead of
> *_read_sp. Is it a direct replacement to replace *_read_sp with
> *_unwind_sp? I didn't see that before I did the commit.

There's currently a catch.

GDB doesn't have a consistent story over what ``info frame'' and "$sp" 
should display for the "sp".  Like the old "$fp", it can end up 
displaying inconsistent values.  I've a partial patch to fix it, need to 
go back though.  However, in the mean time, you can remove read_sp and 
see what happens.

Andrew



      reply	other threads:[~2003-06-20 17:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-20  6:22 Theodore A. Roth
2003-06-20 14:19 ` Andrew Cagney
2003-06-20 17:09   ` Theodore A. Roth
2003-06-20 17:39     ` Andrew Cagney [this message]

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=3EF34557.4090209@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=troth@openavr.org \
    /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