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