3 ms·
If the implementation records the state of your program at each time interval as "the values stored at particular memory locations", it's much simpler to put th
by wyldfire 10y ago
If the implementation records the state of your program at each time interval as "the values stored at particular memory locations", it's much simpler to put those values back at those locations than it would be to recognize the memory map and decompose the state in order to play it back at the arbitrarily established offsets used with ASLR.
As a practical matter, ASLR should have little if any impact to nearly all programs design, so disabling it at development/debug time should not come at a big cost.
BTW this post states "There is no fundamental reason for [ASLR] restriction, but it is some work to fix."
EDIT: I see, your focus is specifically on recording. Disregard this comment, good point.