➜

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 ddvento@ucar.edu, erob, martin.panter, neologix, pitrou, vstinner
Date 2017-09-11.22:04:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1505167478.22.0.793593881679.issue17085@psf.upfronthosting.co.za>
In-reply-to
Content 
Charles-François Natali:
> the crash occurs because the test doesn't reset the alarm (with alarm(0)) upon exit, so if the alarm didn't go off during the test, it comes later when the original signal handler has been reset, and the default handler just exits.
> (...)
> Note that 3.4 and default aren't affected, because the alarm is properly reset.

Right, I fixed this issue in the master branch: I proposed attached PR 3505 to backport the fix.
History
Date User Action Args
2017-09-11 22:04:38vstinnersetrecipients: + vstinner, pitrou, neologix, erob, martin.panter, ddvento@ucar.edu
2017-09-11 22:04:38vstinnersetmessageid: <1505167478.22.0.793593881679.issue17085@psf.upfronthosting.co.za>
2017-09-11 22:04:38vstinnerlinkissue17085 messages
2017-09-11 22:04:38vstinnercreate