Think of it as the "git" for debugging. Take a snapshot, keep going etc ... and then backtrack back to the point where it all started going wrong.
Just very hard to automate easily, yet this uses gdb and all the other macro/command goodness (well, for power users) that gdb comes with.
Think of it as the "git" for debugging. Take a snapshot, keep going etc ... and then backtrack back to the point where it all started going wrong.
Just very hard to automate easily, yet this uses gdb and all the other macro/command goodness (well, for power users) that gdb comes with.