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:	Fri, 16 Jul 2004 10:28:22 -0400
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: coredump on kill
Message-ID:	<20040716142822.GE20693@trixie.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<40F858A3 DOT 8020608 AT hq DOT astra DOT ph>
Mime-Version:	1.0
In-Reply-To:	<40F858A3.8020608@hq.astra.ph>
User-Agent:	Mutt/1.4.1i

On Fri, Jul 16, 2004 at 02:37:23PM -0800, Carlo Florendo y Flora wrote:
>Hello,
>
>Upon invoking the following command, I get a coredump:
>
>/usr/bin/kill --list
>
>By the way, "kill -l" (bash built-in) works.
>
>Attached is cygcheck's output and the dump itself.
>
>Does anyone know of a workaround?

Use kill.exe from a snapshot.  This bug was fixed on 2004-05-27 and the fix will
be in the next version of cygwin.

http://cygwin.com/snapshots/

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/

- Raw text -