From: Qian Hong <fracting@gmail.com>
To: cygwin <cygwin@cygwin.com>
Subject: Re: Randomly hang when compiling Cygwin on Cygwin on Wine
Date: Sun, 01 Nov 2015 19:09:00 -0000 [thread overview]
Message-ID: <CALd+sZTRVMuLjwZMjxN6f6JvTtax5rJAUuk_SMXvcQzMzxhirA@mail.gmail.com> (raw)
In-Reply-To: <CALd+sZS-EbkUMgmRCyJUK0LCMo6zydzB1rbM9iZFrAcnbfHCRQ@mail.gmail.com>
Update:
I have another case of hang:
?(1)-+-bash(1419290)
|-bash(1419318)---make(1423770)---sh(1423783)---sh(1423838)
|-mintty(1249269)---bash(1249277)
|-mintty(47)---bash(55)---bash(1132827)---make(1139169)---sh(1139182)---make(1139234)---sh(1206695)---sh(1206721)---make(1206764)---sh(1206770)---make(1206783)---perl(1249042)
|-mintty(596773)---bash(596790)---pstree(1423865)
`-mintty(1417449)---bash(1417457)
$ ps aux | grep 1249042
1249042 1206783 1132827 1249050 pty0 197608 Oct 31 /usr/bin/perl
1249077 1249042 1132827 1249092 pty0 197608 Oct 31
/usr/bin/nm <defunct>
Here the process perl(1249042) is waiting for a pipe, while its child
process nm(1249077) is in the status "defunct". nm(1249077) appears in
output of `ps aux`, but doesn't appear in output of `pstree -p -l`.
Is there any case, where a child process can exit unexpected, but the
parent process still incorrectly wait for the child process forever?
Thanks!
--
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:[~2015-11-01 19:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 13:28 Qian Hong
2015-11-01 19:09 ` Qian Hong [this message]
2015-11-02 14:30 ` Corinna Vinschen
2016-03-15 14:10 ` Qian Hong
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=CALd+sZTRVMuLjwZMjxN6f6JvTtax5rJAUuk_SMXvcQzMzxhirA@mail.gmail.com \
--to=fracting@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).