Message 385013 - 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	vstinner
Recipients	vstinner
Date	2021-01-13.10:50:12
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1610535013.1.0.942204365805.issue42923@roundup.psfhosted.org>
In-reply-to

Content
When Python cannot report an error and its is not possible to recover from the error, Py_FatalError() displays an error message and exit immediately Python. It's common that Python crashes are coming from third party extension modules, rather than Python itself. Recent example: bpo-42891 crash reported in Python, but it was a bug in lsm-db third party extension module. I propose to enhance Py_FatalError() to attempt to dump the list of extension modules, to ease debugging. I'm working on a PR.

When Python cannot report an error and its is not possible to recover from the error, Py_FatalError() displays an error message and exit immediately Python.

It's common that Python crashes are coming from third party extension modules, rather than Python itself. Recent example: bpo-42891 crash reported in Python, but it was a bug in lsm-db third party extension module.

I propose to enhance Py_FatalError() to attempt to dump the list of extension modules, to ease debugging.

I'm working on a PR.

History
Date	User	Action	Args
2021-01-13 10:50:13	vstinner	set	recipients: + vstinner
2021-01-13 10:50:13	vstinner	set	messageid: <1610535013.1.0.942204365805.issue42923@roundup.psfhosted.org>
2021-01-13 10:50:13	vstinner	link	issue42923 messages
2021-01-13 10:50:12	vstinner	create