4 ms·
My hardest ever bug to debug was a core dump deep in the guts of some nasty c++ code. What's so hard about that? Just load the core dump into a debugger! Wel
by seanhunter 7y ago
My hardest ever bug to debug was a core dump deep in the guts of some nasty c++ code.
What's so hard about that? Just load the core dump into a debugger! Well loading the core dump into the debugger caused the debugger to dump core...
- TeMPOraL 7y agoNot the hardest bug I've had, but working in Common Lisp I've run into macros that crash the runtime (SBCL) when you attempt to see what they expand into. Makes it difficult to debug them.
- chopin 7y agoI can relate. An older version of the Eclipse debugger would run into a stack overflow when the debugged process had a stack overflow and you paused the affected thread. It took me a while to figure that one...
- jiveturkey 7y agosimilar here. bug in jvm ref counting. not only did the java have to be debugged, the jvm itself then had to be debugged. second hardest bug i ever had to deal with. first hardest was a linux kernel crypto bug.