From: Andrew Cagney <cagney@gnu.org>
To: "Dhananjay R. Deshpande" <dhananjayd@KPITCummins.com>
Cc: gdb@sources.redhat.com
Subject: Re: H8300 - Addition of Pseudo registers has broken displaying of CCR and EXR registers
Date: Mon, 01 Dec 2003 16:03:00 -0000 [thread overview]
Message-ID: <3FCB6649.70003@gnu.org> (raw)
In-Reply-To: <69595093233BB547BB70CF5E492B63F202FBC7A0@sohm.kpit.com>
> Hi,
>
> With the addition of Pseudo registers, "info reg" command doesn't show correct values of CCR and EXR registers. If you set these registers from GDB ( set $ccr = 0x55 )then it shows correct value but when the register is modified by instruction it always shows "0". This fails both with SIM and remote target ( stub )
Sounds like it is never fetched, or being fetched from the wrong place
:-( What does "maint print raw-registers" (which dumps the raw state of
the register cache) display? Are you seeing calls to the simulator for
that register?
A testsuite/gdb.arch/ testcase is going to help here. Especially to
ensure that it doesn't break again.
enjoy,
Andrew
next prev parent reply other threads:[~2003-12-01 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-01 13:06 Dhananjay R. Deshpande
2003-12-01 16:03 ` Andrew Cagney [this message]
2003-12-02 13:10 Dhananjay R. Deshpande
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=3FCB6649.70003@gnu.org \
--to=cagney@gnu.org \
--cc=dhananjayd@KPITCummins.com \
--cc=gdb@sources.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