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:	Sun, 26 Jun 2005 00:36:56 +0200 (MET DST)
From:	Angelo Graziosi <Angelo DOT Graziosi AT roma1 DOT infn DOT it>
To:	cygwin AT cygwin DOT com
Subject:	Re: Bash 3.0-2 and kill
In-Reply-To:	<Pine.GSO.4.61.0506241732200.5118@slinky.cs.nyu.edu>
Message-ID:	<Pine.OSF.4.21.0506260014080.7911-100000@ax0rm1.roma1.infn.it>
MIME-Version:	1.0
X-PMX-Version:	4.7.1.128075, Antispam-Engine: 2.0.3.2, Antispam-Data: 2005.6.25.21
X-PerlMx-Spam:	Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __FRAUD_419_BADTHINGS 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0'

Suppose that the command "ps" shows that an application, has a PID
1234 then

    kill -9 1234

kills the application but also the bash (3.0-2), i.e. closes the windows
in which bash is running (for example the dos box or xterm).

In some cases, in $HOME there is bash.exe.stackdump.

After these things I have reinstalled Bash 2.05b-17 with which that
command kills only the application and not bash
(so that one can continue to work without restarting bash).

The system is W2K SP4.

I have almost all Cygwin packages installed (only gcc-test-suite,
ghosthscript native, regex, xwinclip are not installed)

Currently I am usin the snapshot 20050624 (after 20050621), but as I wrote
even with Cygwin 1.5.16-1, 1.5.17-1 bash 3.0-2 is killed.

The Cygwin configuration is quite simple (what setup configures after
installing)

Best regards 
angelo.


On Fri, 24 Jun 2005, 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).
> 
> To help debug this, please provide the exact sequence of commands you used
> to trigger this behavior, as well as the output of "cygcheck -svr" on your
> system.
> 	Igor
> -- 
> 				http://cs.nyu.edu/~pechtcha/
>       |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
> ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
>      |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
>     '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!
> 
> "The Sun will pass between the Earth and the Moon tonight for a total
> Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT
> 


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

- Raw text -