Message143699
| Author |
neologix |
| Recipients |
neologix, rpointel, vstinner |
| Date |
2011年09月07日.18:34:09 |
| SpamBayes Score |
8.1793513e-07 |
| Marked as misclassified |
No |
| Message-id |
<CAH_1eM2sGwTkz2O37iiagMD4-z5BrU7_LPN_R1HvtiAEHZCMKg@mail.gmail.com> |
| In-reply-to |
<1315345576.61.0.523842116768.issue12905@psf.upfronthosting.co.za> |
| Content |
> Using SA_RESTART, read() is not interrupted. But if the program is linked to pthread, read() is always interrupted: with sa_flags=0 or sa_flags=SA_RESTART.
>
Ouch...
>> But OpenBSD's pthread implementation has severe limitations/bugs.
>
> rthread doc contains:
>
> "Future work:
>
> Quite simply, signal handling is one the most complicated aspects of threads to get right. (...)"
>
This paper dates back to 2005, I was hoping they would have solved
this by now...
As for the original problem, IIUC you don't reproduce it with your C
test code...
It might be due to a subtle difference in the way Python is built
(like POSIX_SOURCE...), but it's hard to tell... |
|