This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
RE: [FYI] tutorial for process record and reverse debugging
- From: Marc Khouzam <marc dot khouzam at ericsson dot com>
- To: "'Michael Snyder'" <msnyder at vmware dot com>, "'gdb at sourceware dot org'" <gdb at sourceware dot org>
- Date: Mon, 19 Oct 2009 08:36:39 -0400
- Subject: RE: [FYI] tutorial for process record and reverse debugging
- References: <4ADA4BD8.6080800@vmware.com>
> -----Original Message-----
> From: gdb-owner@sourceware.org
> [mailto:gdb-owner@sourceware.org] On Behalf Of Michael Snyder
> Sent: Saturday, October 17, 2009 6:57 PM
> To: gdb@sourceware.org
> Subject: [FYI] tutorial for process record and reverse debugging
>
> FYI, there is now a tutorial for process record/replay and reverse
> debugging on the gdb wiki:
>
> http://sourceware.org/gdb/wiki/ProcessRecord/Tutorial
Very clearly written. It should be very useful.
I even learned that the following was a wanted behavior:
"We can go directly to the point at which the recording currently ends, by disabling
all our breakpoints and then telling gdb to continue. Process record will replay
until it reaches the current end of the recording, and then stop."
To be honest, I never cared much for this behavior because from an Eclipse
user-experience, it is not very clear why the execution/replay suddenly stops in
this case.
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