Conversely, if you focus on creating a repro you make problems easy.
I’m a little surprised the OP doesn’t mention debuggers. For whatever reason many modern Linux programmers seem to have never and used a debugger and rely almost entirely on printf. Which is utterly bonkers to me! If you can repro and issue and trap it in a debugger then you’ve done 90% of the work.
In those cases, a debugger just can't stop the world, so back to printf it is.
Also time traveling debuggers like WinDbg and rr are the ideal way to debug complex timing issues.
True, but this can be worked around for example with lock free ring buffers etc.
> Also time traveling debuggers like WinDbg and rr are the ideal way to debug complex timing issues.
When applicable rr can be great indeed. Not sure how to apply TTD tools for example in kernel context.
Nice to see Microsoft continues improving WinDbg. (Shame Visual Studio's debugger is so weak in comparison.)