News for hackers. Stuff that matters.
Re:Debugging memory corruption: who the hell writes "2" into... by pm215 on Tuesday December 31, 2024 @10:29AM (#42559244)
I would certainly try with a reverse debugger if I had one, but where the repro instructions are "run this big complex interactive program for 10 minutes" I wouldn't be super confident about successfully recording a repro. At least in my experience with rr the slowdown is enough to make that painful, especially if you need to do multiple "chaos mode" runs to get a timing sensitive bug to trigger. It might still be worth spending time trying to get a faster repro case to make reverse debug a bit more tractable.

There are no comments on this comment yet.