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 martin.panter
Recipients bapt, koobs, martin.panter, python-dev, vstinner
Date 2016-01-27.11:55:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1453895707.7.0.361553825793.issue25868@psf.upfronthosting.co.za>
In-reply-to
Content
(Wrote this ages ago but never hit send:)

Here is another theory to explain the hang: When sigwaitinfo() is being called, and the SIGALRM signal arrives, it executes the signal handler (both the C handler and later the Python handler). If the SIGUSR1 signal arrives while either of these signal handlers are executing, it will be missed, and when sigwaitinfo() resumes it will hang. This would also be avoided by blocking SIGUSR1.

I wonder why the hang only seems to happen with BSD though.
History
Date User Action Args
2016-01-27 11:55:07martin.pantersetrecipients: + martin.panter, vstinner, python-dev, koobs, bapt
2016-01-27 11:55:07martin.pantersetmessageid: <1453895707.7.0.361553825793.issue25868@psf.upfronthosting.co.za>
2016-01-27 11:55:07martin.panterlinkissue25868 messages
2016-01-27 11:55:07martin.pantercreate