Date: Fri, 23 Dec 2005 16:44:58 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Please try a snapshot - final push for 1.5.19
Message-ID: <20051223214458.GA26270@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <20051221162249 DOT GA9890 AT trixie DOT casa DOT cgf DOT cx> <20051223013402 DOT GA3180 AT efn DOT org> <20051223024002 DOT GA31612 AT trixie DOT casa DOT cgf DOT cx> <20051223040718 DOT GA4064 AT efn DOT org> <20051223043507 DOT GA3897 AT trixie DOT casa DOT cgf DOT cx>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20051223043507.GA3897@trixie.casa.cgf.cx>
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Thu, Dec 22, 2005 at 11:35:07PM -0500, Christopher Faylor wrote:
>On Thu, Dec 22, 2005 at 08:07:19PM -0800, Yitzchak Scott-Thoennes wrote:
>>CYGWIN = `tty ntsec title server'
>           ^^^
>Thank you.  That was why I couldn't duplicate it.

I played with this all day and I can't convince myself that it isn't a
readline bug.  It seems like there is a situation where bash/readline
unmasks SIGINT and potentially lets a stray CTRL-C in while the signal
handler is still carefully dealing with signals, causing recursion and,
eventually, an overflow of cygwin's signal stack.

In fact, I could crash bash on linux by doing a:

  while kill -INT nnn; do :; done

where nnn denotes the pid of a running Debian bash 3.00.16(1)-release
binary.

In any event, this isn't a regression and, unless I have an amazing
insight sometime soon, I don't think there is any way to fix this
in the cygwin DLL.

cgf

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