From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: Failures in store.exp caused by regcache
Date: Wed, 08 Jan 2003 19:11:00 -0000 [thread overview]
Message-ID: <3E1C77B4.8070401@redhat.com> (raw)
In-Reply-To: <20030108190506.GA558@nevyn.them.org>
> (Or rather, by the value code's interaction with the regcache)
>
> Andrew, this is more your area; I'd like your advice before I dig any
> further. Here's what's going wrong. Consider the command sequence:
> "up; print u; set u = s_1; print u".
> - u has class LOC_REGISTER
> - The register's home is memory
> - read_var_value therefore returns an lval_memory
> - the value of the register is in the register unwind cache at this point
> - we modify the memory backing the store
> - we have no way to tell that we've just modified the value of a saved
> register on the stack
> - the second print returns the cached value
>
> So, what do we do?
Flush the frame cache.
Andrew
next prev parent reply other threads:[~2003-01-08 19:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 19:05 Daniel Jacobowitz
2003-01-08 19:11 ` Andrew Cagney [this message]
2003-01-09 3:23 ` Daniel Jacobowitz
2003-01-09 16:50 ` Andrew Cagney
2003-01-09 17:14 ` Daniel Jacobowitz
2003-01-09 17:48 ` 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=3E1C77B4.8070401@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.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