[RFA/RFC] Add dump and load command to process record (file format etc)

[Michael Snyder]

Hui Zhu wrote:
> On 2009-08-06, Michael Snyder <msnyder@vmware.com> wrote:

>>  1) Store a pointer to the corefile in the record log file.
>>  2) Store a checksum, hash, or CRC of the corefile in the log file.
> 
> I think this way is easy to implement.
> 
>>  3) Store a CRC of the loadable sections, plus a snapshot of the
>>    register set, in the log file.
>>  4) Store both corefile and log file together in the same file.
> 
> For all of this way, I think we have a problem is when we dump the
> log, we don't know where is the core file.
> Maybe we can extend the record dump command, to let it point out where
> is the  core file or let it call gcore too.

OK, I've written an extension to gcore.c which exports some
functions which we can call from record.c, to save and load
core files for snapshots.

Using this, we can then create an extra section in the core
file, and save our record log in there.

That way, we are assured of consistency between the start state
and the record log, because they are both in the same file.

What do you think?

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: dumpload2.txt
URL: <http://sourceware.org/pipermail/gdb-patches/attachments/20090812/ed8cb94b/attachment.txt>