SIGTSTP and select

Corinna Vinschen
Mon Apr 16 09:52:00 GMT 2007

On Apr 13 15:04, Bob Rossi wrote:
> On Fri, Apr 13, 2007 at 04:51:36PM +0200, Corinna Vinschen wrote:
> > On Apr 13 10:01, Bob Rossi wrote:
> > > On Fri, Apr 13, 2007 at 03:25:01PM +0200, Corinna Vinschen wrote:
> > > > > > On Mon, Apr 02, 2007 at 08:07:23PM -0400, Bob Rossi wrote:
> > When you observed -1/EINTR on Linux, did you install a SIGTSTP signal
> > handle, maybe?
> Hi Corinna,
> Do you think that if I capture the SIGTSTP signal, I could avoid all
> of this? That is, I would somehow avoid the situation where select has
> to deal with being in the blocking state while cgdb recieves the signal?
> I'm not even sure if a process could put itself in the process after
> catching that signal, but if it could, ...

I don't know if you can do this and maintain the job control of the
parent shell.  Using CYGWIN=tty (aka run in a pty) is your best bet,


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

Unsubscribe info:
Problem reports:

More information about the Cygwin mailing list