This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFA/RFC] Add dump and load command to process record and replay
> Date: Sat, 29 Aug 2009 13:33:34 -0700
> From: Michael Snyder <msnyder@vmware.com>
> CC: Hui Zhu <teawater@gmail.com>,
> "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
>
> > Sorry, I don't understand: why would we want to have the record log in
> > a core file? What am I missing here?
>
> Because the record-log itself does not record starting state --
> only changes of state. It is useless by itself if you don't
> restore the starting state first.
>
> Hui's original patch used the "gcore" command to save the
> starting state, and "target core" to restore it.
>
> The problem that I found with that was that it created two
> independent files, core file and record-log file, and that
> there was no way to assure ourselves (or the user) that the
> two files corresponded to one another when they were re-loaded.
>
> That's why I suggested combining them into one file --
> in this implementation, by adding the record-log to an
> extra section in the core file.
Thanks for explaining.
This all needs to be said in the manual (in a form suitable for the
manual, omitting the technicalities and describing this from user
perspective). We cannot just say "dump record log to core file". So
I hereby revoke my approval of the patch for the manual.