4 ms·
IIRC, The gdb team was previously talking implementing this by forking after every instruction. Does anyone know if the current functionality is being built on
by bigmac 17y ago
IIRC, The gdb team was previously talking implementing this by forking after every instruction. Does anyone know if the current functionality is being built on that model?
I guess the advantage of doing it that way is that the majority of the memory pages can be shared if the OS uses a copy-on-write virtual memory system.
This:
Breakpoints and watchpoints will work in reverse -- allowing you for instance to proceed directly to the previous point at which a variable was modified.
is going to absolutely killer functionality for reverse engineers.
- msnyder 17y agoNo, it doesn't fork at all, it simply records the values of registers and memory that will be modified by each instruction, so that they can be restored later.