CODEWITHSUNDEEP
signalsblockingeintr
Martin Sustrik
Martin Sustrik

Reputation: 813

Blocking functions and EINTR

Many POSIX blocking functions return EINTR in case of a signal. The idea is that signal handler sets a flag first (say 'stop' flag in case of SIGINT), then the blocking function unblocks returning EINTR and the application sees the flag and performs orderly shutdown (or whatever).

However, there is no EINTR error for some blocking functions like pthread_mutex_lock and pthread_cond_wait.

What's the idea behind that? How are the applications using these functions supposed to handle signals (Ctrl+C, specifically)?

Upvotes: 5

Views: 2374

Answers (2)

Martin Sustrik
Martin Sustrik

Reputation: 813

No answer. My assumption is that pthread_cond_wait() and SIGINT cannot be combined to perform a clean shutdown. Use sem_wait() or similar instead of pthread_cond_wait().

Upvotes: 2

Chris Dodd
Chris Dodd

Reputation: 126378

In general, only system calls (low level OS calls) return EINTR. Higher level standard library calls do not. So for example, read and write may return EINTR, but printf and gets will not.

Generally, the right thing to do on receiving an EINTR is to redo the call -- that's whythe SA_RESTART flag on signal handlers exists. If you want to handle Ctrl-C, you need to just not ignore the signal. The default action of exiting may be what you want, or you can write your own signal handler to do something else.

Upvotes: 0

Related Questions