Search Results for "replay"

rr aspires to be your primary C/C++ debugging tool for Linux, replacing — well, enhancing — gdb. You record a failure once, then debug the recording, deterministically, as many times as you want. The same execution is replayed every time. rr also provides efficient reverse execution under gdb. Set breakpoints and data watchpoints and quickly reverse-execute to where they were hit. rr works on real applications and is used by many developers to fix real bugs. It makes debugging hard bugs much...

...ADP stores details of the path taken by your script and variables and their values in a SQLITE3 database. The current release supports LIVE running. A future release will support DEAD running. In DEAD runs you’ll be able to replay a LIVE run from the database recording, which means that you can start at any point and travel in either direction and the value of the variables will be those that were current at that point of time in the LIVE run. Imagine your script crashed and you can replay from there backwards, and see how you got there and the values the variables had. ...

...Once a capture of a target application has been made, GAPID lets you disconnect from the target and inspect all the graphics commands made by the application. GAPID is able to replay the command stream, letting you visualize the frame composition by stepping through each command and inspecting the driver state at any point in the stream. Replay also supports modifications, allowing you to adjust command parameters and shader source to instantly see what effect this would have on the frame. GAPID can also visualize the textures, shaders and draw call geometry used by the application.

Make GDB can record a log of the process execution, and replay it with both forward and reverse execute commands. It's in GDB main trunk now. To get more message: http://sourceware.org/gdb/wiki/ReversibleDebugging

Lizard is a debugger that lets you step forwards as well as backwards through the execution of your program. Lizard is a replay debugger: the program is run to completion under a tracer first, and then the replay stage begins.