From: Pedro Alves <pedro@codesourcery.com>
To: Marc Khouzam <marc.khouzam@ericsson.com>
Cc: "'gdb@sourceware.org'" <gdb@sourceware.org>,
"'Greg Law'" <glaw@undo-software.com>,
"'Hui Zhu'" <teawater@gmail.com>,
"'Michael Snyder'" <msnyder@vmware.com>,
"'gdb-patches ml'" <gdb-patches@sourceware.org>
Subject: Re: PRecord sets memory even when it says it did not
Date: Mon, 14 Sep 2009 18:01:00 -0000 [thread overview]
Message-ID: <200909141901.08651.pedro@codesourcery.com> (raw)
In-Reply-To: <F7CE05678329534C957159168FA70DEC515363D089@EUSAACMS0703.eamcs.ericsson.se>
On Monday 14 September 2009 18:53:51, Marc Khouzam wrote:
>
> > -----Original Message-----
> > From: Pedro Alves [mailto:pedro@codesourcery.com]
> > Sent: Monday, September 14, 2009 1:50 PM
> > To: gdb@sourceware.org
> > Cc: Greg Law; Hui Zhu; Marc Khouzam; Michael Snyder; gdb-patches ml
> > Subject: Re: PRecord sets memory even when it says it did not
> >
> > > Could this be related to the caching changes that have happened
> > > recently? i.e. does the cache get updated even though the
> > underlying
> > > poke operation failed? If so, this issue would seem to be
> > wider than
> > > just prec (and wider than reverse, too).
> >
> > If so, then there's an easy way to find out: try again with
> > "set stack-cache off".
> >
>
> Yes, that seems to fix everything.
Then I'd suspect either a bug dcache_xfer_memory, or a missing
target_dcache_invalidate/dcache_invalidate call somewhere.
--
Pedro Alves
next prev parent reply other threads:[~2009-09-14 18:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F7CE05678329534C957159168FA70DEC5153600749@EUSAACMS0703.eamcs.ericsson.se>
2009-09-14 4:40 ` Hui Zhu
2009-09-14 13:52 ` Marc Khouzam
2009-09-14 17:17 ` Michael Snyder
2009-09-14 17:21 ` Marc Khouzam
2009-09-14 17:26 ` Michael Snyder
2009-09-14 15:53 ` Daniel Jacobowitz
2009-09-14 16:15 ` Hui Zhu
2009-09-14 17:10 ` Marc Khouzam
2009-09-14 17:10 ` Greg Law
2009-09-14 17:19 ` Marc Khouzam
2009-09-14 17:50 ` Pedro Alves
2009-09-14 17:54 ` Marc Khouzam
2009-09-14 18:00 ` Michael Snyder
2009-09-14 18:01 ` Pedro Alves [this message]
2009-09-14 18:02 ` Michael Snyder
2009-09-14 18:15 ` Pedro Alves
2009-09-14 18:21 ` Michael Snyder
2009-09-14 18:36 ` Pedro Alves
2009-09-14 19:04 ` Doug Evans
2009-09-14 19:08 ` Michael Snyder
2009-09-14 20:36 ` Pedro Alves
2009-09-14 21:08 ` Doug Evans
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=200909141901.08651.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=gdb@sourceware.org \
--cc=glaw@undo-software.com \
--cc=marc.khouzam@ericsson.com \
--cc=msnyder@vmware.com \
--cc=teawater@gmail.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