Re:Debugging memory corruption: who the hell writes “2” into...
by anaisbetts on Sunday November 14, 2021 @08:49AM
(#29217142)
Problems like this (though for this particular app it might be hard because it's Too Big), Time-Travel Debugging is practically made for it - https://docs.microsoft.com/en-us/windows-hardware/drivers/de... - hit your first corruption, set the memory breakpoint, then just go backwards
[ Parent
| on HN ]
Re:Debugging memory corruption: who the hell writes “2” into...
by drmeister on Sunday November 14, 2021 @02:59PM
(#29220102)
This should be the top response. With a time traveling debugger this would take 15 minutes to solve (minus the time to make the crash happen). On linux I use the Undo debugger - I don't own stock - I just love the product.