Martin Panter added the comment: 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25868> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
