To my surprise, some programmers consider using print statements instead of debuggers as a wholly inferior means of debugging. As I view the debugging process, they are complementary techniques. But the issue is not really “print statements” versus “debuggers.” - It’s traces versus snapshots. / HN

Here’s one of its most important use cases. Have you ever had you debugger stupified by a NULL function pointer before? Debuggers aren’t very good at handling this situation. Because once the control flow jumps to the NULL page, you’d need to find a way to rewind execution history to figure out how it got there. - Logging C Functions

see also

• Time Travel Debugger
• Logging C Functions - features of the Cosmopolitan Libc runtime is its –ftrace flag that logs C function calls.
  • Debugging C with Cosmopolitan Libc / HN
• Error Context – a stack trace for data
• Boost.Stacktrace