This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

System calls getting interrupted with signals, even with SA_RESTART

Hey guys,

I've ran into a little problem. I have been porting an piece of software to
Cygwin. It builds and initially runs fine, but when I get a SIGALRM signal,
which I use for asynchronous timers, a few things return with an EINTR:

-IPC semaphores (using CygIPC)

Note that I am asserting SA_RESTART when I set up the signal handler. The
procedure I take is this:
struct sigaction SigAction;
memset(&SigAction, 0, sizeof(struct sigaction));
SigAction.sa_handler = Internal_Act_HandleTimers;
SigAction.sa_flags = SA_RESTART; //restart system calls interrupted with
this signal

if(sigaction(SIGALRM, &SigAction, NULL) < 0)
    leprintf(LOGGING_SELF, LVL_SYSERR, "Error initing SIGALRM handler");
    return false;
siginterrupt(SIGALRM, false);

The error returned from select is: (errno, strerror(errno)
   errno - 4 (Interrupted system call)
(obviously ENTR)

Obviously the signal handler is set up correctly, and when just asserting
SA_RESTART didn't work, I tried sticking a call to siginterrupt in there as
well, but had no luck there either.

Is it just a stupid mistake on my end, or something I'm failing to see? The
only other thing that might be the case is that the restarting of select and
the semaphore stuff isn't implemented?

TIA for ANY help!!

Robby Dermody (
phase9 industries, inc. -

We confide in our strength, without boasting of it; we respect that of
others, without fearing it.
    -Thomas Jefferson

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]