Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.programming.threads > #1989
| From | Markus Elfring <Markus.Elfring@web.de> |
|---|---|
| Newsgroups | comp.programming.threads, comp.unix.programmer |
| Subject | Re: Clarification for the handling of sigwaitinfo() |
| Date | 2013-11-17 10:50 +0100 |
| Message-ID | <berhqoFao4nU1@mid.individual.net> (permalink) |
| References | <bepgirFsghjU1@mid.individual.net> <20131116202321.6916e6ad@bother.homenet> |
Cross-posted to 2 groups.
> I may have missed it (the code is quite dense) but I could not see > on a quick read where you blocked asynchronous delivery of the signal to > the process, so that sigwait() could pick it up. I thought that my function call "pthread_sigmask(SIG_SETMASK, &signal_set, NULL)" does this. Did I interpret the return value of the function "sigwaitinfo" in the wrong way here? Regards, Markus
Back to comp.programming.threads | Previous | Next — Previous in thread | Next in thread | Find similar
Clarification for the handling of sigwaitinfo() Markus Elfring <Markus.Elfring@web.de> - 2013-11-16 16:16 +0100
Re: Clarification for the handling of sigwaitinfo() Chris Vine <chris@cvine--nospam--.freeserve.co.uk> - 2013-11-16 20:23 +0000
Re: Clarification for the handling of sigwaitinfo() Markus Elfring <Markus.Elfring@web.de> - 2013-11-17 10:50 +0100
Re: Clarification for the handling of sigwaitinfo() Chris Vine <chris@cvine--nospam--.freeserve.co.uk> - 2013-11-17 11:11 +0000
Re: Clarification for the handling of sigwaitinfo() Markus Elfring <Markus.Elfring@web.de> - 2013-11-17 13:30 +0100
csiph-web