X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Wed, 7 Mar 2012 12:43:21 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: 1.7.10 cygrunsrv.exe fails with "fork: 11, Resource temporarily unavailable" Message-ID: <20120307114321.GA14210@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <4F51BDA2.1040108@cygwin.com> <20120304114922.GA18852@calimero.vinschen.de> <20120305163158.GT18852@calimero.vinschen.de> <4F54F8D6.3040203@cwilson.fastmail.fm> <20120305173953.GW18852@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20120305173953.GW18852@calimero.vinschen.de> User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Mar 5 18:39, Corinna Vinschen wrote: > On Mar 5 12:33, Charles Wilson wrote: > > On 3/5/2012 11:31 AM, Corinna Vinschen wrote: > > > Why this only fails when cygrunsrv has been built with gcc-4 but not with > > > gcc-3 is most puzzeling. > > > > $ cygcheck /usr/bin/cygrunsrv.exe > > C:\cygwin\bin\cygrunsrv.exe > > C:\cygwin\bin\cygwin1.dll > > C:\WINDOWS\system32\KERNEL32.dll > > C:\WINDOWS\system32\ntdll.dll > > C:\WINDOWS\system32\ADVAPI32.DLL > > C:\WINDOWS\system32\RPCRT4.dll > > C:\WINDOWS\system32\Secur32.dll > > C:\WINDOWS\system32\USER32.dll > > C:\WINDOWS\system32\GDI32.dll > > C:\cygwin\bin\cyggcc_s-1.dll <<<<< > > C:\cygwin\bin\cygstdc++-6.dll <<<<< > > > > When built with gcc3, we didn't have runtime dlls so everything was > > static. Maybe just building cygrunsrv with -static-libgcc > > -static-libstdc++ ? > > BTDT. That doesn't help at all, unfortunately. But thanks for your > input. More ideas welcome :-} I just released a new cygrunsrv which fixes the problem for me. What it does is to fork in a separate pthread, for which the stack has been set up in the application heap. This reduceds the chance for collision a lot. Please give it a try. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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