Maybe it's just me but I just use a proper debugger. Debugpy and VSCode work fantastically. In a previous company I set things up so that when there's an uncau

Maybe it's just me but I just use a proper debugger. Debugpy and VSCode work fantastically. In a previous company I set things up so that when there's an uncaught exception it will automatically start a VSCode debug session and connect to it. Here's the extension: https://github.com/Timmmm/autodebug/ https://github.com/Timmmm/autodebug/ Unfortunately the Python part of that is not open source but it was only a few lines of code - should be easy to recreate. That repo does contain a C library that does a similar thing. You might just say "why not just run your program directly with the debugger?" and yeah that is better when you can do it, but I'm working with complicated silicon verification flows that are often several layers of Python and Make, followed by a simulator (e.g. Questa or VCS) that itself loads the library you want to debug. Very difficult to make debugging work through all those layers, but it's quite easy to write some code at the bottom of the stack that says to a debugger "I'm here, debug me!".