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 docs@python, eric.araujo, vstinner
Date 2011-05-30.00:23:35
SpamBayes Score 0.002632057
Marked as misclassified No
Message-id <1306715016.35.0.971142062232.issue12209@psf.upfronthosting.co.za>
In-reply-to
Content
What do you call a "stack trace"? I use this term in the C language, especially when using the "where" command of gdb. In Python, the stack trace is called a "traceback". Anyway, faulthandler prints the Python trace, not the C trace, so I prefer to call it a "traceback" than "stack trace".

faulthandler.dump_traceback() output is similar to:

    try:
        raise ValueError()
    except:
        exctype, value, tb = sys.exc_info()
        traceback.print_tb(tb)

faulthandler doesn't print the line from the script, only the function name, file name and line number; and the first line is different.
History
Date User Action Args
2011-05-30 00:23:36vstinnersetrecipients: + vstinner, eric.araujo, docs@python
2011-05-30 00:23:36vstinnersetmessageid: <1306715016.35.0.971142062232.issue12209@psf.upfronthosting.co.za>
2011-05-30 00:23:35vstinnerlinkissue12209 messages
2011-05-30 00:23:35vstinnercreate