On Mon, Jun 4, 2018 at 11:05 AM, Per Jessen
ah, well. sem_wait() isn't safe to call either, only sem_post(). Should have been obvious, duh.
We used to use signals in our 'real-time' data collection programs. We did, at some point, add threads into the mix. I think the problem is if the signal handler itself has anything at all to do with thread/mutex control. If threads/mutexes and signals are separate, then there is no problem (IMO). Of course we have eliminated all signal stuff. It was really more appropriate on unicore processors. When processors started having multiple cores (threads of control), threads make more sense. And the code is easier to follow/maintain. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-programming+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-programming+owner@opensuse.org