Message128680
| Author | vstinner |
|---|---|
| Recipients | db3l, gregory.p.smith, pitrou, rnk, sable, vstinner |
| Date | 2011-02-16.16:55:03 |
| SpamBayes Score | 3.6414204e-07 |
| Marked as misclassified | No |
| Message-id | <1297875297.18444.14.camel@marge> |
| In-reply-to | <1297873451.52.0.539569284841.issue11223@psf.upfronthosting.co.za> |
| Content | |
|---|---|
> I will try with pdb or something. You can also try to attach gdb to the running process: with python-gdb.py, you have nice py-* commands. Or if you don't have gdb7, you may try my faulthandler module: you will have to modify the source code (eg. Lib/test/regrtest.py) to add at the top: import faulthandler, signal; faulthandler.register(signal.SIGUSR1) Then you can display the current Python backtrace by sending a SIGUSR1 signal to the running Python process (eg. killall -USR1 python). https://github.com/haypo/faulthandler/wiki |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011-02-16 16:55:10 | vstinner | set | recipients: + vstinner, gregory.p.smith, db3l, pitrou, sable, rnk |
| 2011-02-16 16:55:04 | vstinner | link | issue11223 messages |
| 2011-02-16 16:55:03 | vstinner | create | |