➜

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 2017-10-06.20:35:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1507322101.2.0.213398074469.issue31719@psf.upfronthosting.co.za>
In-reply-to
Content 
On the s390x architecture, the test_regrtest.test_crashed() fails because Python doesn't crash.

test.support._crash_python() calls ctypes.string_at(0) to crash Python. In debug mode, ctypes.string_at(0) fails with an assertion error and the process is killed with the SIGABRT signal. In release mode, ctypes.string_at(0) returns an empty string but doesn't crash.

Attached PR adds a new _testcapi._read_null() function which does crash in a reliable way on s390x and x86 :-) The function uses the C "volatile" keyword to prevent compiler optimizations. I copied the code from my faulthandler._read_null() function in the master branch which was battle tested. It does crash on all platforms... except of AIX.
History
Date User Action Args
2017-10-06 20:35:01vstinnersetrecipients: + vstinner
2017-10-06 20:35:01vstinnersetmessageid: <1507322101.2.0.213398074469.issue31719@psf.upfronthosting.co.za>
2017-10-06 20:35:01vstinnerlinkissue31719 messages
2017-10-06 20:35:00vstinnercreate