2 ms·
When I was at Microsoft, at least among several of the better developers, when debugging an issue, many would just ignore source code and enter a bunch of "u" (
by asveikau 11y ago
When I was at Microsoft, at least among several of the better developers, when debugging an issue, many would just ignore source code and enter a bunch of "u" (disassemble) commands into windbg. This is IMHO a great habit if you're writing C or C++. In many cases it ensures less distance between you and a bad pointer dereference. Your code, my code, source code, or none - doesn't matter. Just look at the faulting address and see what it expects.
From a certain vantage point, in these languages, if you aren't seeing assembly from time to time, you're not seeing reality.
Consequently, I kind of chuckle when I hear people say they can't debug optimized builds.