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 Michael.Felt, vstinner
Date 2021-03-30.07:40:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1617090006.69.0.157120669533.issue43665@roundup.psfhosted.org>
In-reply-to
Content
A core dump is a very bad sign of health.

Can you please try to bisect which test is causing the segfault using bisect_cmd? Try the command:

./python -m test.bisect_cmd -o bisect --fail-env-changed test_importlib

The command should takes 10-60 minutes, and you should see the number of tests decreasing. I hope that at the end, the command will identify a single method triggering the crash.

At the end, the create "bisect" file contains the test methods causing the bug.

Then you can re-run tests with:

./python -m test --fail-env-changed test_importlib --matchfile=bisect


> The core dump is caused by SIGTRAP. I need help to learn how to stop the core dump from being cleaned up so I can load it into dbx and hopefully understand/learn with sub-test is actually having issues.

You can re-run the test without libregrtest by running it directly. Example:

./python -m test.test_importlib test_spec.Frozen_ModuleSpecMethodsTests.test_reload -v

It should create a core dump in the current directory, or you run the command in your favorite debugger.


My notes on debugging a Python crash: https://pythondev.readthedocs.io/debug_tools.html#core-dump
History
Date User Action Args
2021-03-30 07:40:06vstinnersetrecipients: + vstinner, Michael.Felt
2021-03-30 07:40:06vstinnersetmessageid: <1617090006.69.0.157120669533.issue43665@roundup.psfhosted.org>
2021-03-30 07:40:06vstinnerlinkissue43665 messages
2021-03-30 07:40:06vstinnercreate