Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Xinan Tang" <xinan@tidalnetworks.net>
To: <gdb@sources.redhat.com>
Subject: "which function is called when updating a register?"
Date: Fri, 16 Jul 2004 21:46:00 -0000	[thread overview]
Message-ID: <KAEHILJLFHMPJPLKAFBHIEJOCBAA.xinan@tidalnetworks.net> (raw)
In-Reply-To: <vt21xkgz2vu.fsf@zenia.home>

Hi

  I set breakpoints on both:

	-- gdbsim_fetch_register and
      -- gdbsim_store_register

  when single stepping the instruction execution, I noticed that
gdbsim_fetech_register was called but gdbsim_store_register.

  Which function is actually called to update a register content within gdb
using a built-in simulator?

Thanks

--Xinan
__________________________________________________
"Xinan Tang" <xinan@tidalnetworks.net> writes:
>
> > target sim

Then the code in gdb/remote-sim.c would be a good thing to look at.
In particular, are the right values coming through
gdbsim_fetch_register and gdbsim_store_register?


  reply	other threads:[~2004-07-16 21:40 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   ` Xinan Tang [this message]
2004-07-18 20:38     ` "which function is called when updating a register?" Andrew Cagney
2004-07-19 18:50       ` Xinan Tang
2004-07-19 18:59         ` Andrew Cagney
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=KAEHILJLFHMPJPLKAFBHIEJOCBAA.xinan@tidalnetworks.net \
    --to=xinan@tidalnetworks.net \
    --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