4 ms·
Debuggers are not great when you have a bug that occurs between multiple CPU cores, hardware device timing, etc. In those cases, a debugger just can't stop the
by vardump 2y ago
Debuggers are not great when you have a bug that occurs between multiple CPU cores, hardware device timing, etc.
In those cases, a debugger just can't stop the world, so back to printf it is.
- forrestthewoods 2y agoprintf also mucks with sensitive timing issues. So it’s not great either. Also time traveling debuggers like WinDbg and rr are the ideal way to debug complex timing issues.
- vardump 2y ago> printf also mucks with sensitive timing issues. So it’s not great either. 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.)
- Neikius 2y agoWell I am aware there are ring 0 debuggers out there. Also running in a VM could help. Question is is there anything useful around you could just grab (for linux)? It should be possible at last.