public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: pdt@dontech.dk
Cc: cygwin@cygwin.com
Subject: Re: fork: Resource temporarily unavailable errors after upgrading cygwin packages
Date: Thu, 13 Feb 2020 04:14:00 -0000	[thread overview]
Message-ID: <20200213131322.66b104901134c644c0dad57e@nifty.ne.jp> (raw)
In-Reply-To: <3971cde6277a16cb04ac25067b4478b9cfbfa319.camel@dontech.dk>

On Wed, 12 Feb 2020 11:54:02 +0100
Peter Dons Tychsen wrote:
> Hi Takashi,
> 
> On Wed, 2020-02-12 at 11:24 +0900, Takashi Yano wrote:
> > My failure in pty code was that I used kill() in pty system
> > calls. kill() can be used check if the process is still alive
> > by passing signal number of 0 to the second argument. It returns
> > -1 if the process already exited. However, in this case errno
> > is set to ESRCH. As a result, the errno value which pty system
> > call set is accidentally overwritten by kill().
> 
> OK, thanks for clearing all that up. Just wanted to make sure kill()
> was not buggy :-).
> 
> I will test the committed patch and the upcoming release vigerously to
> see if there are still bugs to be found in this area. Not sure why i
> get fork() errors and you do not (my tests with the example i made
> always causes fork() errors in 3.1.2).
> 
> Thanks for all the help and your snappy replies,

Could you please try latest snapshot?
https://cygwin.com/snapshots/

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

--
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

  parent reply	other threads:[~2020-02-13  4:14 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6d43c714-c4ba-4f0c-9913-cb8453129c85@gmail.com>
     [not found] ` <d24aa066-ab3d-9ff0-215a-0a1ed1ec2e5d@cornell.edu>
2020-01-01 22:32   ` David Finnie
2020-01-01 23:43     ` David Finnie
2020-01-02  3:02       ` Ken Brown
2020-01-02 21:58       ` Peter Dons Tychsen
2020-01-02 22:29         ` David Finnie
2020-01-02 22:40           ` Ken Brown
2020-02-05 21:46           ` Peter Dons Tychsen
2020-02-05 22:07             ` Ken Brown
2020-02-06  0:07               ` Takashi Yano
2020-02-05 22:18             ` David Finnie
2020-02-05 22:31               ` Ken Brown
2020-02-05 23:07                 ` David Finnie
2020-02-05 23:35                   ` Ken Brown
2020-02-07 18:13                     ` Brian Inglis
2020-02-07 21:44                       ` David Finnie
2020-02-10 20:58               ` Peter Dons Tychsen
2020-02-10 21:34                 ` David Finnie
2020-02-11  2:21                 ` Takashi Yano
2020-02-11 10:38                   ` Peter Dons Tychsen
2020-02-11 10:40                     ` Peter Dons Tychsen
2020-02-11 13:16                     ` Takashi Yano
2020-02-11 14:21                       ` Ken Brown
2020-02-12 14:40                         ` Takashi Yano
2020-02-11 21:31                       ` Peter Dons Tychsen
2020-02-12  2:25                         ` Takashi Yano
2020-02-12  7:50                           ` Corinna Vinschen
     [not found]                         ` <20200212112411.32f05ee5ce2c1401bd076746@nifty.ne.jp>
     [not found]                           ` <3971cde6277a16cb04ac25067b4478b9cfbfa319.camel@dontech.dk>
2020-02-13  4:14                             ` Takashi Yano [this message]
2020-02-13 21:42                               ` Peter Dons Tychsen
2020-02-14  1:25                                 ` Takashi Yano

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=20200213131322.66b104901134c644c0dad57e@nifty.ne.jp \
    --to=takashi.yano@nifty.ne.jp \
    --cc=cygwin@cygwin.com \
    --cc=pdt@dontech.dk \
    /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).