From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: fork: Resource temporarily unavailable errors after upgrading cygwin packages
Date: Wed, 12 Feb 2020 07:50:00 -0000 [thread overview]
Message-ID: <20200212075043.GK4442@calimero.vinschen.de> (raw)
In-Reply-To: <20200212112458.291ccf7a64109d23374d2a73@nifty.ne.jp>
[-- Attachment #1: Type: text/plain, Size: 1431 bytes --]
On Feb 12 11:24, Takashi Yano wrote:
> On Tue, 11 Feb 2020 22:31:12 +0100
> Peter Dons Tychsen wrote:
> > On Tue, 2020-02-11 at 22:16 +0900, Takashi Yano wrote:
> > > however, I found the real cause is that errno is accidentally set
> > > by kill() in pty system calls. That is, the problem is not in the
> > > kill() itself but in usage of it. Cygwin older than 3.1.0 does not
> > > have these code in pty.
> >
> > OK, is there a fix for that or is that the fix you already pushed? And
> > what is wrong with the usage of kill(). How can kill() be used
> > incorrectly?
>
> POSIX system calls set global variable errno to appropriate
> value when the system calls fail.
> http://man7.org/linux/man-pages/man3/errno.3.html
>
> 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().
>
> The patch was already accepted and pushed to git repository.
> I hope cygwin 3.1.3 which applied this patch will be released
> shortly.
For a first test, please try the latest developer snapshot on
https://cygwin.com/snapshots/
Thanks,
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-02-12 7:50 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 [this message]
[not found] ` <20200212112411.32f05ee5ce2c1401bd076746@nifty.ne.jp>
[not found] ` <3971cde6277a16cb04ac25067b4478b9cfbfa319.camel@dontech.dk>
2020-02-13 4:14 ` Takashi Yano
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=20200212075043.GK4442@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).