3 ms·
I have debugged plenty of memory bugs without using a debugger. Debugging multithreaded/async code is an entirely deeper level of hell, and there's been plenty
by userbinator 4y ago
I have debugged plenty of memory bugs without using a debugger.
Debugging multithreaded/async code is an entirely deeper level of hell, and there's been plenty of times where just having a debugger attached was enough to make the code work, or building unoptimised/with debugging information. On the other hand, carefully placed prints can catch the culprit without affecting the timing so much that the bug disappears.