This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
RE: PRecord sets memory even when it says it did not
- From: Marc Khouzam <marc dot khouzam at ericsson dot com>
- To: "'Pedro Alves'" <pedro at codesourcery dot com>, "'gdb at sourceware dot org'" <gdb at sourceware dot org>
- Cc: "'Greg Law'" <glaw at undo-software dot com>, "'Hui Zhu'" <teawater at gmail dot com>, "'Michael Snyder'" <msnyder at vmware dot com>, "'gdb-patches ml'" <gdb-patches at sourceware dot org>
- Date: Mon, 14 Sep 2009 13:53:51 -0400
- Subject: RE: PRecord sets memory even when it says it did not
- References: <F7CE05678329534C957159168FA70DEC5153600749@EUSAACMS0703.eamcs.ericsson.se> <daef60380909132139k46f577aet63f4089a97138368@mail.gmail.com> <4AAE7910.5040907@undo-software.com> <200909141849.57563.pedro@codesourcery.com>
> -----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.