On Jan 13, 2015, at 8:26 AM, Skip Montanaro <skip.montan...@gmail.com> wrote:
> Assuming you have gdb available, you should be able to attach to the > running process, then set a breakpoint in relevant functions (like > exit() or abort()). Once there, you can pick through the C stack > manually (kind of tedious) or use the gdbinit file which comes with > Python to get a Python stack trace (much less tedious, once you've > made sure any version dependencies have been eliminated). Or, with the > latest versions of gdb (7.x I think), you get more stuff built into > gdb itself. > > More details here: > > https://wiki.python.org/moin/DebuggingWithGdb Thanks, I'll look into that. Hopefully running with the debugger attached won't slow things down to much. The main thing I think will be getting the python extensions installed - the instructions only talk about doing this for linux packages. > > Skip -- https://mail.python.org/mailman/listinfo/python-list