This is the mail archive of the
mailing list for the GDB project.
Re: vmware's replay framework and gdb
- From: Michael Snyder <msnyder at vmware dot com>
- To: Edward Peschko <horos11 at gmail dot com>
- Cc: "gdb at sourceware dot org" <gdb at sourceware dot org>
- Date: Wed, 05 Nov 2008 17:12:55 -0800
- Subject: Re: vmware's replay framework and gdb
- References: <firstname.lastname@example.org>
Edward Peschko wrote:
> I watched the following Google tech talk with much interest:
> It describes a very generic, scalable, environment-agnostic way of
> recording programs' execution via vmware's virtualization, and doing
> reverse tracing (which is one of the reasons I'd like to record
> programs in the first place). I heard gdb mentioned in the video in
> passing, so I'm assuming someone in the list is familiar with vmware's
Me -- I'm a member of the replay debugging team at VMware,
and a public gdb maintainer, and I was at that tech talk.
> but how far along is gdb in supporting this framework?
I'm working on it. ;-)
If you look at the recent threads on this list about reverse
debugging in gdb, you'll get an idea of where we're headed.
We want to let a user debug a recorded execution, deterministic-
ally, and make it run both forward and backward using the same
reverse debugging commands as described in those threads
(reverse-continue, reverse-step, reverse-next etc.)
We don't have any product release date for it, but you can
already do some rudimentary replay debugging with the
released version of VMware Worksatation and the standard gdb.
Here's a blog article about it: