From: Andrew Cagney <cagney@gnu.org>
To: Xinan Tang <xinan@tidalnetworks.net>
Cc: gdb@sources.redhat.com
Subject: Re: "which function is called when updating a register?"
Date: Mon, 19 Jul 2004 18:59:00 -0000 [thread overview]
Message-ID: <40FC17E1.4050007@gnu.org> (raw)
In-Reply-To: <KAEHILJLFHMPJPLKAFBHMEKICBAA.xinan@tidalnetworks.net>
> Hi
>
> Thanks for the reply.
>
> My problem is that after I building a new target, I could not see the
> registers being updated except PC. For example, after I did "set $sp =
> 0x80001000", and then "info reg", I still saw $sp is ZERO.
>
> I am trying to fig out what was wrong with my build. One way to do this is
> to trace the simulator execution. However I don't have a clear picture about
> the interface between the simulator execution and gdb. For example, which
> data structures are read by "info reg" command and which ones are touched by
> the simulator. How could GDB get those register content being updated by the
> simulator?
When the inferior (simulator) is resumed, GDB flushes its internal
register cache (target_registers_changed). This causes GDB to always
fetch the latest register values found in the simulator.
Andrew
next prev parent reply other threads:[~2004-07-19 18:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <KAEHILJLFHMPJPLKAFBHAEDFCBAA.xinan@tidalnetworks.net>
2004-06-16 1:53 ` "Info reg doesn't work" Jim Blandy
2004-07-16 21:46 ` "which function is called when updating a register?" Xinan Tang
2004-07-18 20:38 ` Andrew Cagney
2004-07-19 18:50 ` Xinan Tang
2004-07-19 18:59 ` Andrew Cagney [this message]
2004-07-21 5:24 ` "Add sim memory region by default" Xinan Tang
2004-07-21 15:48 ` Dave Korn
2004-07-21 17:53 ` Xinan Tang
2004-07-21 19:15 ` "igen based simulators doc.?" Xinan Tang
2004-07-21 20:24 ` "igen vs. cgen?" Xinan Tang
2004-07-22 9:35 ` Monika Chaddha
2004-07-22 19:12 ` Xinan Tang
2004-07-23 8:11 ` Monika Chaddha
2004-07-23 19:03 ` "igen based simulators doc.?" Andrew Cagney
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=40FC17E1.4050007@gnu.org \
--to=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=xinan@tidalnetworks.net \
/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).