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.y...@nifty.ne.jp> -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
