Re: fork() fails if it is called recursively from a child thread.

2017-03-21 Thread Erik Bray
On Sat, Mar 11, 2017 at 2:29 AM, Takashi Yano wrote: > Hello, > > On Fri, 10 Mar 2017 21:10:36 +0100 Corinna Vinschen wrote: >> Thanks for the report and especially the testcase. >> >> It was a tricky problem to debug so it took me a while, but I think >> I got it now. >> >> I uploaded new develope

Re: fork() fails if it is called recursively from a child thread.

2017-03-10 Thread Takashi Yano
Hello, On Fri, 10 Mar 2017 21:10:36 +0100 Corinna Vinschen wrote: > Thanks for the report and especially the testcase. > > It was a tricky problem to debug so it took me a while, but I think > I got it now. > > I uploaded new developer snapshots to https://cygwin.com/snapshots/ > > Please give

Re: fork() fails if it is called recursively from a child thread.

2017-03-10 Thread Corinna Vinschen
Hi, On Mar 9 20:39, Takashi Yano wrote: > Hello, > > I found fork() fails if it is called recursively from a child thread. > > Simple test case, attached (fk.c), reproduces this problem. > > Expected result: > Parent 0 [22034] exit. > Child 0 [22036] works. > Pa

Re: fork() fails if it is called recursively from a child thread.

2017-03-09 Thread cyg Simple
On 3/9/2017 12:33 PM, Takashi Yano wrote: > Thanks for your reply. > > On Thu, 09 Mar 2017 18:06:44 +0100 Achim Gratz wrote: > >> Takashi Yano writes: >>> 0 [main] a 4668 fork: child -1 - forked process 8456 died >>> unexpectedly, retry 0, exit code 0xC142, errno 11 >> >> Not sure if t

Re: fork() fails if it is called recursively from a child thread.

2017-03-09 Thread Takashi Yano
Thanks for your reply. On Thu, 09 Mar 2017 18:06:44 +0100 Achim Gratz wrote: > Takashi Yano writes: > > 0 [main] a 4668 fork: child -1 - forked process 8456 died > > unexpectedly, retry 0, exit code 0xC142, errno 11 > > Not sure if that helps, but that error says that some DLL could n

Re: fork() fails if it is called recursively from a child thread.

2017-03-09 Thread Achim Gratz
Takashi Yano writes: > 0 [main] a 4668 fork: child -1 - forked process 8456 died unexpectedly, > retry 0, exit code 0xC142, errno 11 Not sure if that helps, but that error says that some DLL could not be initialized. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andr

Re: fork() fails if it is called recursively from a child thread.

2017-03-09 Thread Takashi Yano
On Thu, 9 Mar 2017 08:53:19 -0500 Eliot Moss wrote: Thank you for response. > This strikes me as either BLODA (interfering software) or a need to > rebase some dll(s). That's what I most commonly see that causes that > fork error. This occurs even under newly installed windows 10 & 7. Moreover,

Re: fork() fails if it is called recursively from a child thread.

2017-03-09 Thread Eliot Moss
On 3/9/2017 6:39 AM, Takashi Yano wrote: > Hello, > > I found fork() fails if it is called recursively from a child thread. > > Simple test case, attached (fk.c), reproduces this problem. > > Expected result: > Parent 0 [22034] exit. > Child 0 [22036] works. > Pa

fork() fails if it is called recursively from a child thread.

2017-03-09 Thread Takashi Yano
Hello, I found fork() fails if it is called recursively from a child thread. Simple test case, attached (fk.c), reproduces this problem. Expected result: Parent 0 [22034] exit. Child 0 [22036] works. Parent 1 [22036] exit. Child 1 [22038] works. Parent 2 [22038] exit. Child 2 [22039] works