From: Doug Henderson <djndnbvg@gmail.com>
To: cygwin <cygwin@cygwin.com>
Subject: Re: Problem with zombie processes
Date: Fri, 17 Feb 2017 15:06:00 -0000 [thread overview]
Message-ID: <CAJ1FpuPdAC2jkMPTo+gxqpd=_7qZ9WB3t3KWizZyWMtcNNiwVA@mail.gmail.com> (raw)
In-Reply-To: <CAOTD34Z7VM=6=Ss_gCLS97c4sFNpnaT-+RgJq+xme-VyWYbbpw@mail.gmail.com>
On 17 February 2017 at 04:00, Erik Bray wrote:
> On Tue, Feb 14, 2017 at 8:25 PM, Mark Geisert wrote:
>> Erik Bray wrote:
>>>
>>> The attached Python script
>>
>>
>> ??
>
> D'oh! Here is the script. It at least demonstrates the problem.
>
If you add a few "time.sleep(1)" statements before and after sending
the kill signals, you should observe consistent behavior. Without the
delay (and forced context switches) the main process may run before
the child process state has settled before and after the kill signals.
On Win7, with the delays, I see consistent behavior for both cases.
Test 1 always succeeds. Test 2 always fails with "IOError or OSError
[Errno 22] invalid argument" for python or python3 (respectively).
While not a explanation of the different results for test1 and test2, I HTH.
Doug
--
Doug Henderson, Calgary, Alberta, Canada - from gmail.com
--
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:[~2017-02-17 15:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 11:14 Erik Bray
2017-02-14 19:25 ` Mark Geisert
2017-02-17 11:00 ` Erik Bray
2017-02-17 15:06 ` Doug Henderson [this message]
2017-02-17 22:06 ` Mark Geisert
2017-02-20 9:46 ` Erik Bray
2017-02-20 10:54 ` Mark Geisert
2017-02-20 15:23 ` Erik Bray
2017-02-20 22:54 ` Mark Geisert
2017-02-21 11:59 ` Erik Bray
2019-04-04 12:44 ` E. Madison Bray
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='CAJ1FpuPdAC2jkMPTo+gxqpd=_7qZ9WB3t3KWizZyWMtcNNiwVA@mail.gmail.com' \
--to=djndnbvg@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).