Re:Use the Surrender Tactic: Frustration when debugging
by greenyoda on Saturday March 30, 2013 @04:08PM
(#5466503)
Sometimes bugs are genuinely hard to debug and appear in hostile environments. Many people who have been programming for a long time have seen bugs that take much longer than five days to debug. For example:
- The bug doesn't reproduce when run under the debugger (not so uncommon with C code). Or the bug goes away when you change the timing of the code by writing to a log file.
- The bug could be in code that you didn't write and don't yet completely understand; the people who wrote the code have all left the company.
- The bug can be in a third-party library that you don't even have the source code to. You can only infer what the library is doing by seeing how it reacts to what you're passing it. Or you can try disassembling its code.
- The bug can be due to bad machine code generated by a compiler.
- The bug can be due to undocumented behavior in an operating system.
- The bug could be in a really complex algorithm.
- The bug might only reproduce at a customer's site with the customer's confidential data.
- The bug might be sporadic, perhaps depending on certain patterns of network traffic.
- The bug could be due to a fundamental misunderstanding of the original project requirements that will only become apparent after days of investigation.
- The bug doesn't reproduce when run under the debugger (not so uncommon with C code). Or the bug goes away when you change the timing of the code by writing to a log file.
- The bug could be in code that you didn't write and don't yet completely understand; the people who wrote the code have all left the company.
- The bug can be in a third-party library that you don't even have the source code to. You can only infer what the library is doing by seeing how it reacts to what you're passing it. Or you can try disassembling its code.
- The bug can be due to bad machine code generated by a compiler.
- The bug can be due to undocumented behavior in an operating system.
- The bug could be in a really complex algorithm.
- The bug might only reproduce at a customer's site with the customer's confidential data.
- The bug might be sporadic, perhaps depending on certain patterns of network traffic.
- The bug could be due to a fundamental misunderstanding of the original project requirements that will only become apparent after days of investigation.