This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: GDB record patch 0.1.3.1 for GDB-6.8 release
On Wed, May 21, 2008 at 03:35:16PM -0300, Thiago Jung Bauermann wrote:
> On Wed, 2008-05-21 at 11:10 -0700, Michael Snyder wrote:
> > If you want to improve on that a little bit more, you might
> > say "If you change the machine state in the middle of a
> > replay, I will throw away all of the recorded state *forward*
> > of that point, but keep the recorded state going *back* from
> > there. You can't go back into what used to be the "future"
> > because by changing the past, you have now destroyed that
> > particular future. But you can still go further into the
> > past.
>
> Right. And that's very easy to implement right? Just throw away the
> recorded entries "in the future". Or am I being to naïve?
It depends... hey, weren't you at my talk about this last June? :-)
I don't remember if I went into this part but there's a section in the
proceedings. Continuing forward from a modified point depends on
being able to synchronize external and recorded state. Just
destroying the recorded state would work if you could detect
relevant modifications - it's made slightly tricky by memory
breakpoints but you're right, it's not too hard.
--
Daniel Jacobowitz
CodeSourcery