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 steve.dower
Recipients lukasz.langa, pablogsal, paul.moore, pitrou, steve.dower, tim.golden, vstinner, zach.ware
Date 2019-02-27.19:42:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1551296564.82.0.733646549437.issue36116@roundup.psfhosted.org>
In-reply-to
Content
It's also possible that the child process is causing the segfault because of misconfiguration (e.g. broken environment variables).

And depending on the OS, abort() calls (via Py_FatalError) sometimes appear to be segfaults, so it could be any number of issues. (Aside - I'd love to replace the abort() calls with specific exit codes for configuration errors - they really mess up the crash data we see on Windows.)

I'll try some tests locally to see if this is reproducible, but if anyone can extract the original stdout/stderr from the buildbot, that would be helpful.
History
Date User Action Args
2019-02-27 19:42:44steve.dowersetrecipients: + steve.dower, paul.moore, pitrou, vstinner, tim.golden, lukasz.langa, zach.ware, pablogsal
2019-02-27 19:42:44steve.dowersetmessageid: <1551296564.82.0.733646549437.issue36116@roundup.psfhosted.org>
2019-02-27 19:42:44steve.dowerlinkissue36116 messages
2019-02-27 19:42:44steve.dowercreate