X-Spam-Check-By:	sourceware.org
Date:	Mon, 16 Apr 2007 11:52:33 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: SIGTSTP and select
Message-ID:	<20070416095233.GA21503@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20070403000723 DOT GG24160 AT cox DOT net> <20070403003753 DOT GA11244 AT ednor DOT casa DOT cgf DOT cx> <20070403141320 DOT GA3459 AT cox DOT net> <20070413132501 DOT GG15801 AT calimero DOT vinschen DOT de> <20070413140108 DOT GA25914 AT cox DOT net> <20070413145136 DOT GK15801 AT calimero DOT vinschen DOT de> <20070413190408 DOT GE25914 AT cox DOT net>
Mime-Version:	1.0
In-Reply-To:	<20070413190408.GE25914@cox.net>
User-Agent:	Mutt/1.4.2.2i
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

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,
probably.


Corinna

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

--
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/

- Raw text -