Message 132304 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	pitrou
Recipients	Arfrever, Trundle, dmalcolm, lemburg, pitrou, scott.dial, vstinner
Date	2011-03-27.10:22:35
SpamBayes Score	0.0040017907
Marked as misclassified	No
Message-id	<1301221355.91.0.252046240463.issue11393@psf.upfronthosting.co.za>
In-reply-to

Content
I have pushed a new branch "faulthandler-thread" in http://hg.python.org/features/faulthandler/. It contains an implementation of dump_tracebacks_later() using a watchdog thread, instead of alarm(). It has two advantages: - it works under Windows - it won't disrupt use of alarm() or SIGALRM by user code (including the test suite) It has one drawback: you can only display all threads, since the watchdog thread is not a Python thread. I haven't fixed the tests for it, I'm waiting for Victor's changes first ;)

I have pushed a new branch "faulthandler-thread" in http://hg.python.org/features/faulthandler/. It contains an implementation of dump_tracebacks_later() using a watchdog thread, instead of alarm().

It has two advantages:
- it works under Windows
- it won't disrupt use of alarm() or SIGALRM by user code (including the test suite)

It has one drawback: you can only display all threads, since the watchdog thread is not a Python thread.

I haven't fixed the tests for it, I'm waiting for Victor's changes first ;)

History
Date	User	Action	Args
2011-03-27 10:22:36	pitrou	set	recipients: + pitrou, lemburg, scott.dial, vstinner, Arfrever, Trundle, dmalcolm
2011-03-27 10:22:35	pitrou	set	messageid: <1301221355.91.0.252046240463.issue11393@psf.upfronthosting.co.za>
2011-03-27 10:22:35	pitrou	link	issue11393 messages
2011-03-27 10:22:35	pitrou	create