When the Debugger Lies

Reminds me of the time when visual studio would show one value of a variable, but print would show a different one. Never trusted VS again after that.

Nice writeup. WinDbg has the same stale-cache trap on live Windows targets.

Very cool! I love reading about details like this.

Debuggers can lie pretty often. Especially if you are just doing things with ASM. I had some issues with V8 debugging and the debugger just saying that a function got called which for sure wasn't. Even with the option that V8 should emit gdb info :/

Once upon a time I had to figure out an issue where I forgot a `return` statement at the end of a non-`void` function, so the C++ compiler happily omitted both RETs for some reason and let the program go straight into illegal instructions. That was fun to debug (not fun, I practically had to single-step through the entire program) because every time this happened the debugger was incredibly confused about what the fuck was going on and nothing made any sense.