From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: GNU make losing jobserver tokens
Date: Sun, 1 May 2022 09:51:41 +0900 [thread overview]
Message-ID: <20220501095141.b7e39c9f08e413d49aa4fdc2@nifty.ne.jp> (raw)
In-Reply-To: <cac5432b-4cca-406a-7c9f-b4288dacfd0b@cornell.edu>
On Sat, 30 Apr 2022 17:51:03 -0400
Ken Brown wrote:
> On 4/29/2022 5:10 AM, Takashi Yano wrote:
> > On Thu, 28 Apr 2022 17:32:22 +0200
> > I tried to move sigproc_init() call from dll_crt0_0() to
> > fork::child() for 64bit cygwin, however, that causes hang
> > at cygwin startup.
> >
> > Am I missing somehting?
>
> I've never looked into the Cygwin startup code, so just ignore me if what I say
> is nonsense.
>
> Currently sigproc_init is called either from dll_crt0_0 or from dll_crt0_1,
> depending on the value of dynamically_loaded. What would happen if you always
> call it from dll_crt0_1, right after
>
> cygwin_finished_initializing = true;
Thanks for the advice.
That causes hang on cygwin startup due to fork() fail :(
--
Takashi Yano <takashi.yano@nifty.ne.jp>
prev parent reply other threads:[~2022-05-01 0:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 14:28 Magnus Ihse Bursie
2022-03-21 15:09 ` Ken Brown
2022-03-22 6:54 ` Noel Grandin
2022-03-22 17:52 ` GNU make losing jobserver tokens in pipes Brian Inglis
2022-03-22 19:38 ` checking cyg version (was Re: GNU make losing jobserver tokens) L A Walsh
2022-03-22 21:58 ` Adam Dinwoodie
2022-03-22 23:06 ` Mark Geisert
2022-03-23 17:47 ` Samuel Lelièvre
2022-03-23 6:24 ` GNU make losing jobserver tokens Roumen Petrov
2022-04-01 8:45 ` Takashi Yano
2022-04-27 14:13 ` Takashi Yano
2022-04-28 13:42 ` Ken Brown
2022-04-28 14:09 ` Corinna Vinschen
2022-04-28 15:01 ` Takashi Yano
2022-04-28 15:32 ` Corinna Vinschen
2022-04-29 9:10 ` Takashi Yano
2022-04-30 21:51 ` Ken Brown
2022-05-01 0:51 ` Takashi Yano [this message]
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=20220501095141.b7e39c9f08e413d49aa4fdc2@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--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).