New blog post: Debugging an evil Go runtime bughttps://marcan.st/2017/12/debugging-an-evil-go-runtime-bug/ …
-
If it doesn't make assumptions about stack layout or use of libc, then quite likely. I was going to mention reverse execution debugging as a powerful approach that might've worked but I wasn't sure of any examples.
Ah, no. It emulates a single core machine. Wouldn't repro the failure, it requires multicore (not just multithread).
-
-
rr's chaos mode plays with thread scheduling enough that it might be able to tease out the bug anyways.
-
The orq is atomic on a single core CPU, it's never going to race anything because it's a single instruction and you can't interrupt a thread in the middle of the orq.
- Show replies
New conversation -
-
-
Ahh right, yes.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Also looks like it monkeypatches vDSO syscalls (which is natural, since it needs to fake them for replay), which would also break things there.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.