RE: [FYI] tutorial for process record and reverse debugging

Marc Khouzam
2009-10-19T13:06:46Z

> -----Original Message-----
> From: gdb-owner@sourceware.org
> [mailto:gdb-owner@sourceware.org] On Behalf Of Hui Zhu
> Sent: Monday, October 19, 2009 8:57 AM
> To: Marc Khouzam
> Cc: Michael Snyder; gdb@sourceware.org
> Subject: Re: [FYI] tutorial for process record and reverse debugging
>
> > But from reading the tutorial I see that it may be of
> interest in some situations.
> > What bothers me though is that one must disable all
> breakpoints and then re-enable
> > them.  This can be a bit of an annoyance, especially if
> some bps were already disabled.
> > I got to wonder if this doesn't call for a new command;
> something like
> > "record live", which would take us to the end of the
> recording while not needing the
> > user to deal with existing breakpoints.
> >
> > What do you think?
> >
> > Marc
> >
>
> Sorry Marc, I cannot understand it. Could you please tell me which
> status need "disable all breakpoints and then re-enable them"?

In the tutorial, around the middle of section
"Continue, reverse-continue, and breakpoints"
it mentions that after doing some reverse execution, we may be
"now ready to resume where we left off".

From what I understand this means that the user may decide that she
is done with reverse execution and wants to go back to executing
the live program. To do this, we need to disable all bps, do a
'continue' and then (optionally) re-enable all bps.

If going straight to the end of the recording log is a valuable
feature, I was thinking it may deserve its own command.

Ultimately, I'm hoping that with such a command, we can then see
if we can have PRecord directly jump from recorded execution
to live execution without stopping.

I'm hoping to get opinions from you experts, as I'm not sure it is
a good idea.

Marc