SIGTSTP and select

[Bob Rossi <bob_rossi at cox dot net>]

Hi,

I'm preparing a new release of CGDB and I'm testing it out on several
platforms. I noticed a bug and tracked it down to SIGTSTP and select.

I'm not exactly sure what has changed since the last release to cause
this issue. However, here it is.

CGDB has a select loop that it uses as it's main loop. Since CGDB is a
ncurses application, the user can type ctrl-z and it is put into the
background. Then if the user types 'fg' it should resume like normal.

When ctrl-z is typed, CGDB receives a SIGTSTP on both linux and cygwin.
When CGDB is at the select loop and this happens on linux select returns
-1 and errno is set to EINTR. My code simple does a 'continue' when this
happens and the select loop is reentered. All works well. On cygwin,
select does not return with -1. (I didn't check the return value but I
can, I just compare to -1 in an if statement). In fact, select also
detects that input is ready on stdin. This causes CGDB to get to a read
system call (which is non blocking) and the read system call fails with
errno set to EAGAIN. This causes CGDB to exit.

The main loop looks something like this,
  if (select (max + 1, &rset, NULL, NULL, NULL) == -1)
    { 
      if (errno == EINTR)
        continue;
      ..
    }

  if (FD_ISSET (STDIN_FILENO, &rset)) {
    handle_stdin
  }

So, my question is, is there a bug with select on cygwin? Is select
working properly and I should handle the read call differently? Why does
it act differently than linux?

Sorry if this question is obvious to everyone else, it isn't to me.

Thanks,
Bob Rossi

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/