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 vstinner
Recipients David.Edelsohn, db3l, gvanrossum, larry, ncoghlan, neologix, pitrou, python-dev, sbt, skrah, vstinner
Date 2013-10-21.00:19:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1382314772.17.0.241582154154.issue19293@psf.upfronthosting.co.za>
In-reply-to
Content
[Off-topic: Heck, another one of those upside-down tracebacks. WHY???]

faulthandler is really a very low-level module. I wrote it to analyze deadlocks, memory corruptions and other sad cases. faulthandler is designed to provide as much information as possible even if Python internals are corrupted. So it only reads data structures, without processing them too much. For example, frames are stored from the most recent to the oldest. faulthandler also truncates long traceback to 100 frames (write "..." if there are more), to stop the loop if there is a cycle in the chained list of frames.

The documentation also mentions other limitations:
http://docs.python.org/dev/library/faulthandler.html
History
Date User Action Args
2013-10-21 00:19:32vstinnersetrecipients: + vstinner, gvanrossum, db3l, ncoghlan, pitrou, larry, skrah, neologix, python-dev, sbt, David.Edelsohn
2013-10-21 00:19:32vstinnersetmessageid: <1382314772.17.0.241582154154.issue19293@psf.upfronthosting.co.za>
2013-10-21 00:19:31vstinnerlinkissue19293 messages
2013-10-21 00:19:31vstinnercreate