From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Exitcode is 0 when killing a cygwin initiated process via taskmanager
Date: Tue, 23 Dec 2014 07:41:00 -0000 [thread overview]
Message-ID: <54991CB8.8020904@gmail.com> (raw)
In-Reply-To: <CAMhmPJ1P12vuK1gXhL=25p5GbSGbahZGY+4co+bzUFG96iXK8g@mail.gmail.com>
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
next prev parent reply other threads:[~2014-12-23 7:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 2:34 -
2014-12-23 7:41 ` Marco Atzeri [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-12-23 11:09 -
2014-12-23 11:37 ` Marco Atzeri
2014-12-23 13:00 ` -
2014-12-23 19:47 ` cyg Simple
2014-12-24 1:56 ` -
2014-12-23 0:38 -
2014-12-23 1:50 ` Andrey Repin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54991CB8.8020904@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).