Message104725
One open question regarding interaction with threading. sigprocmask's behavior in a multithreaded program is unspecified. pthread_sigmask should be used instead. I could either expose both of these and let the caller choose, or I could make signal.sigprocmask use pthread_sigmask if it's available, and fall back to sigprocmask. I don't see any disadvantages of doing the latter, and the former seems like it would create an attractive nuisance. However, I don't have much experience with sigprocmask; I'm only interested in it because of its use in combination with signalfd. |
|
Date |
User |
Action |
Args |
2010-05-01 15:22:05 | exarkun | set | recipients:
+ exarkun, loewis, spiv, pitrou, marcin.bachry |
2010-05-01 15:22:05 | exarkun | set | messageid: <1272727325.36.0.978018433689.issue8407@psf.upfronthosting.co.za> |
2010-05-01 15:22:03 | exarkun | link | issue8407 messages |
2010-05-01 15:22:03 | exarkun | create | |
|