Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Kalpana Ramamurthy" <kal_pana@hotmail.com>
To: gdb-patches@sources.redhat.com
Cc: kal_pana@hotmail.com
Subject: Why is the state of cache being changed by regcache_observer_notify_target() ?
Date: Tue, 29 May 2007 12:13:00 -0000	[thread overview]
Message-ID: <BAY144-F34710C6C4A51828E9DF760E82F0@phx.gbl> (raw)

I am changing a register like this :
$sp = (long long *)$pa

When value_assign() is called in valops.c, it goes to put_frame_register() 
to set the modified
contents of register SP. While doing this, it sets the registers_valip_p to 
1 in
register_raw_write() after copying over the modified values in the buffer to 
the regcache.

memcpy (register_buffer (regcache, regnum), buf, 
regcache->descr->sizeof_register[regnum]) ;
regcache->register_valid_p[regnum] = 1 ;

But soon after in value_assign(), it calls for 
observer_notify_target_changed() which in turn
calls regcache_observer_target_changed(). This calls for register_changed() 
that immediately
resets the value of register_valid_p to 0. And when register_valid_p is set 
to 0, it indicates that
it is not cached but is fetchable and hence tries to fetch the target 
registers again. Something
which I cannot understand gets messed up after that.

But if I comment out the call to observer_notify_target_changed() in 
value_assign(), everything
works fine and the value of $sp is changed as per what I want.

Why is the regcache_observer_target_changed() changing the values of 
register_valid_p as soon as its set earlier ?

Kalpana
===

_________________________________________________________________
Catch all the cricketing action right here. Live score, match reports, 
photos et al. http://content.msn.co.in/Sports/Cricket/Default.aspx


             reply	other threads:[~2007-05-29 12:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29 12:13 Kalpana Ramamurthy [this message]
2007-05-31 17:35 ` Daniel Jacobowitz

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=BAY144-F34710C6C4A51828E9DF760E82F0@phx.gbl \
    --to=kal_pana@hotmail.com \
    --cc=gdb-patches@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