Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Date: Sat, 25 Jun 2005 11:26:39 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Bash 3.0-2 and kill
Message-ID: <20050625152639.GB30463@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <Pine DOT OSF DOT 4 DOT 21 DOT 0506242313310 DOT 4860-100000 AT ax0rm1 DOT roma1 DOT infn DOT it> <Pine DOT GSO DOT 4 DOT 61 DOT 0506241732200 DOT 5118 AT slinky DOT cs DOT nyu DOT edu> <20050624223131 DOT GA27592 AT trixie DOT casa DOT cgf DOT cx> <Pine DOT GSO DOT 4 DOT 61 DOT 0506250041120 DOT 18734 AT slinky DOT cs DOT nyu DOT edu> <42BD72A8 DOT 105 AT byu DOT net> <20050625152204 DOT GA30463 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: <20050625152204.GA30463@trixie.casa.cgf.cx>
User-Agent: Mutt/1.5.8i

On Sat, Jun 25, 2005 at 11:22:04AM -0400, Christopher Faylor wrote:
>On Sat, Jun 25, 2005 at 09:05:12AM -0600, Eric Blake wrote:
>>According to Igor Pechtchanski on 6/24/2005 10:50 PM:
>>>>Given that if cygwin was this broken all sorts of other things would be
>>>>broken as well, this is more likely a problem with bash.
>>>
>>>One reason for my guess was that I recalled discussions of bash using
>>>pretty specialized spawn techniques, and it was likely to have some
>>>corner case interaction with signal handling that normal programs
>>>wouldn't encounter.  There may also be something different about the
>>>SIGCHLD that bash is getting when the child is killed with SIGKILL.
>>>But that was no more than a guess, and yes, it's quite possible that
>>>there's a bug in the bash signal handler.
>>
>>I wouldn't at all be surprised if it is a bash bug, since I blindly
>>forward-ported the job handling tweaks made for cygwin in 2.05b-17 to
>>3.0 without seeing what else changed upstream in 3.0.  I am still
>>trying to reproduce the crash with a debugging build to get a
>>stacktrace, and haven't succeeded at it yet, so a more exact formula
>>from the OP would indeed be useful.  Also, for those who have seen the
>>crash, please include in your report what "set -o" and "shopt" display,
>>since some of the shell options affect the job handling behavior.
>
>This seems reproducible:
>
>  c:\>gdb bash
>  (gdb) r
>  bash-3.00$ sleep 300&
>  bash-3.00$
>
>In another window kill the sleep's, then hit enter at the bash prompt
                                   ^
                                    pid
>and you should see a SIGSEGV.

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