X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=xTWN50d0C0dsamL1u8YRTrPjexCWCbaFwGFkmWu6dV0
	v/AdRA5p5mIj05HXeBq5y7+FNxuOxA/8l2DaNjBx9fWMRetJ4RlcNk6QcMH2EsOn
	3TuA+t8wkehQkv4aSTMHCw1jPEUD8b3nTJvZaGJpeUrm1LDIg7ifEI97aJskkhxo
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=EobkZ1X2z/5t9fSWnupaN7DJLYo=; b=B11fT2mgs72pIiWmm
	+3Ne2xTx749iQq/IYaDID76IwLzRmwD6+U9GNWw9ZBms6RamJVsJIgFmdAyOltOS
	O13YOikJ5OFUcOwa5E7faz/tq5c5h+LgrkqG8mnt1KWy330DXmcu4yUWqXTwY5Ib
	Y7O4Md0oFLkFgda0uq3PznFsy8=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO: mail-wg0-f51.google.com
X-Received: by 10.194.19.234 with SMTP id i10mr6424555wje.40.1419320513630;        Mon, 22 Dec 2014 23:41:53 -0800 (PST)
Message-ID: <54991CB8.8020904@gmail.com>
Date: Tue, 23 Dec 2014 08:41:44 +0100
From: Marco Atzeri <marco DOT atzeri AT gmail DOT com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Exitcode is 0 when killing a cygwin initiated process via taskmanager
References: <CAMhmPJ1P12vuK1gXhL=25p5GbSGbahZGY+4co+bzUFG96iXK8g AT mail DOT gmail DOT com>
In-Reply-To: <CAMhmPJ1P12vuK1gXhL=25p5GbSGbahZGY+4co+bzUFG96iXK8g@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 12/23/2014 3:33 AM, - wrote:
> Hi,
>
>>> Any idea how to solve (get the "canceled" exit code? Remember: The
>>> script continues like a normal finish of the command)
>
>> What do you mean by "canceled" exit code, pretty please?
>
> oh, any exitcode <> 0 would be nice. Sending sigkill on debian gives a 137.
>
> The point is, I rely on having a successfully executed command, if
> exitcode is 0. In this case command is terminated, left garbage and
> did not do its job and I go on like everything would be fine. How
> should error checking care about such a condition / state?
>
> Any ideas? And by the way, is such a condition in pure GNU/Linux
> producible? Sigkill is quite brute force exit isn't it?

no. It is just the standard way, you ask the program to kill itself.
In that case

result: 143

Using Taskmanager is brute force as cygwin dll can not act
and correctly manage the exitcode

Regards
Marco


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple