reverse-debugging

You may be familiar with ReplayDirector, http://www.replaysolutions.com/products/replaydirector-for-java-ee Chronon, http://www.chrononsystems.com/products/chronon-time-travelling-debugger they both advertise themselves as 'Java DVRs' - are there any open-source implementations that offer similar (even a subset of their) features? The only ones I know of are WhyLine Not open source yet, but may eventually be, free download though Omniscient Debugger Jive Diver TOD Omniscient debuggers record the trace data to query afterwards. They are often also called reverse-, back-in-time, bidirectional-

I get the following message in gdb (version 7.1): [Thread debugging using libthread_db enabled] and the command reverse-step results with the following error message: (gdb) reverse-step Target multi-thread does not support this command I am debugging a serial code right now, so I definitely do not need multi-threading. Can I turn this off somehow so that I get the latest reverse-debug commands to work? Also, if the code is parallelised with OpenMPI, there will be no need for multi-thread debugging at all, right? Edit: Is this set as a compilation flag that can be just excluded? You don't

I'm trying to use the reverse debugging features of gdb 7.3.1 on a multi-threaded project (using libevent), but I get the following error: (gdb) reverse-step Target multi-thread does not support this command. From this question , I thought perhaps that it was an issue loading libthread_db but, when I run the program, gdb says: Starting program: /home/robb/slug/slug [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/libthread_db.so.1". How can I enable reverse debugging with gdb 7.3.1 on a multi-threaded project? Is it possible? Kevin To do this, you need to

(EDIT: per the first answer below the current "trick" seems to be using an Atom processor. But I hope some gdb guru can answer if this is a fundamental limitation, or whether there adding support for other processors is on the roadmap?) Reverse execution seems to be working in my environment: I can reverse-continue, see a plausible record log, and move around within it: (gdb) start ...Temporary breakpoint 5 at 0x8048460: file bang.cpp, line 13. Starting program: /home/thomasg/temp/./bang Temporary breakpoint 5, main () at bang.cpp:13 13 f(1000); (gdb) record (gdb) continue Continuing.