From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17406 invoked by alias); 23 Dec 2014 07:41:58 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 17390 invoked by uid 89); 23 Dec 2014 07:41:57 -0000 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 Received: from mail-wg0-f51.google.com (HELO mail-wg0-f51.google.com) (74.125.82.51) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Tue, 23 Dec 2014 07:41:56 +0000 Received: by mail-wg0-f51.google.com with SMTP id x12so8254909wgg.24 for ; Mon, 22 Dec 2014 23:41:53 -0800 (PST) X-Received: by 10.194.19.234 with SMTP id i10mr6424555wje.40.1419320513630; Mon, 22 Dec 2014 23:41:53 -0800 (PST) Received: from [192.168.0.5] (ppp-193-167.32-151.iol.it. [151.32.167.193]) by mx.google.com with ESMTPSA id wv8sm26569465wjc.44.2014.12.22.23.41.51 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 22 Dec 2014 23:41:52 -0800 (PST) Message-ID: <54991CB8.8020904@gmail.com> Date: Tue, 23 Dec 2014 07:41:00 -0000 From: Marco Atzeri 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@cygwin.com Subject: Re: Exitcode is 0 when killing a cygwin initiated process via taskmanager References: In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2014-12/txt/msg00343.txt.bz2 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