Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
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
Date: Fri, 24 Jun 2005 18:31:31 -0400
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Bash 3.0-2 and kill
Message-ID: <20050624223131.GA27592@trixie.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
References: <Pine.OSF.4.21.0506242313310.4860-100000@ax0rm1.roma1.infn.it> <Pine.GSO.4.61.0506241732200.5118@slinky.cs.nyu.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.61.0506241732200.5118@slinky.cs.nyu.edu>
User-Agent: Mutt/1.5.8i

On Fri, Jun 24, 2005 at 05:38:02PM -0400, Igor Pechtchanski wrote:
>On Fri, 24 Jun 2005, Angelo Graziosi wrote:
>
>> I have noted that when one uses
>>
>>    kill -9 <process-PID>
>>
>> in bash 3.0-2 (test), the command kills the process but also bash (even
>> if one uses /bin/kill...).
>>
>> In bash 2.05b-17 that command kills only the process.
>>
>> These things happen with
>>
>>    cygwin 1.5.16-1
>>    cygwin 1.5.17-1
>>    snaps. 20050615
>>    snaps. 20050617
>>    snaps. 20050621
>>
>> (I have listed only the snaps I tried)
>>
>> Which is the normal behaviour (3.0-2 or 2.05b-17)?
>
>Unless the <process-PID> refers to the bash process itself, it seems that
>the behavior of 3.0-2 is wrong.  Not sure if it's a bash bug, or a Cygwin
>signal handling bug exposed by bash (the behavior of /bin/kill seems to
>point toward the latter).

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.  Running bash
under zsh and trying a few kill -9's I finally got bash to exit with a
"segmentation fault", which is more likely to be a problem with bash
than with cygwin.

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/