Message 256456 - Python tracker

➜

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	2015-12-15.10:58:02
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1450177083.06.0.575863975244.issue25868@psf.upfronthosting.co.za>
In-reply-to

Content
You would only block SIGUSR1 (the signal being waited for). SIGALRM would remain unblocked, so the syscall should be interrupted by it. If everything is working smoothly, you should generally see two SIGALRM interrupts per sleep time, so I don’t think it is worth changing to three. I guess you could increment a counter in the SIGALRM handler to verify that it gets called multiple times in the vicinity of the sigwaitinfo() call.

You would only block SIGUSR1 (the signal being waited for). SIGALRM would remain unblocked, so the syscall should be interrupted by it.

If everything is working smoothly, you should generally see two SIGALRM interrupts per sleep time, so I don’t think it is worth changing to three.

I guess you could increment a counter in the SIGALRM handler to verify that it gets called multiple times in the vicinity of the sigwaitinfo() call.

History
Date	User	Action	Args
2015-12-15 10:58:03	martin.panter	set	recipients: + martin.panter, vstinner, python-dev, koobs, bapt
2015-12-15 10:58:03	martin.panter	set	messageid: <1450177083.06.0.575863975244.issue25868@psf.upfronthosting.co.za>
2015-12-15 10:58:03	martin.panter	link	issue25868 messages
2015-12-15 10:58:02	martin.panter	create