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
Message-ID: <42BFF786.40306@byu.net>
Date: Mon, 27 Jun 2005 06:56:38 -0600
From: Eric Blake <ebb9@byu.net>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Bash 3.0-2 and kill
References: <Pine.OSF.4.21.0506242313310.4860-100000@ax0rm1.roma1.infn.it>
In-Reply-To: <Pine.OSF.4.21.0506242313310.4860-100000@ax0rm1.roma1.infn.it>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Angelo Graziosi on 6/24/2005 3:26 PM:
> 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...).
> 

I have gotten to the point where I am seeing reproducible crashes in a
plain debugging version of bash inside gdb, but that the problem appears
to be malloc'd memory corruption (I hate those bugs - they are so hard to
pinpoint).  I now have to attempt to build a malloc-debugging version of
bash, and see where bash is corrupting the heap.

- --
Life is short - so eat dessert first!

Eric Blake             ebb9@byu.net
cygwin bash maintainer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCv/eG84KuGfSFAYARAmDAAJ93n5jZc4nYPDiC+iSQEa2enXTI0QCeLRtx
BQFprLBCY1F1EPUzdiCEong=
=JenQ
-----END PGP SIGNATURE-----

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