[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
readline signal bug
From: |
Eric Blake |
Subject: |
readline signal bug |
Date: |
Fri, 23 Dec 2005 22:09:19 +0000 |
This was reported on the cygwin list. I don't know if bash-3.1/
readline-5.1 have fixed the issue or not. I also don't have
access to a debian machine to try reproducing it myself.
-------------- Forwarded Message: --------------
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Please try a snapshot - final push for 1.5.19
Date: Fri, 23 Dec 2005 21:45:56 +0000
>
> 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.
>
- readline signal bug,
Eric Blake <=