Earlier quoted context omitted.
Hardware breakpoints on memory accesses. This is a somewhat common technique for tracing the value of a variable backwards in time in native code, particularly in the presence of buffer overflows or other memory corruption. When debugging, you find out that a variable has a weird value, a value it could never have according to the code. So you put a hardware breakpoint on the variable's address and restart the progra…
On Linux you could try using the Fast Reversible Debugger ( https://github.com/fred-dbg/fred ) for its memory-accurate record/replay feature. Full disclosure: I was a contributor on that project at one point.
I've never heard of DMTCP or FReD. It sounds interesting. Have you thought of submitting it to HN?