X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Tue, 18 Mar 2008 10:58:19 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Strange pthread_atfork() behavior Message-ID: <20080318095819.GU19345@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <200803172248 DOT 47653 DOT alon DOT barlev AT gmail DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200803172248.47653.alon.barlev@gmail.com> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Mar 17 22:48, Alon Bar-Lev wrote: > When running under cygwin the exec program runs after about 60 seconds. > The following is the output: > > __atfork_prepare > __atfork_parent > before sleep > __atfork_child > after sleep > > > 56 [main] a 2952 sig_send: wait for sig_complete event failed, signal -34, rc 258, Win32 error 0 at child > > > Any clue? Looks like a bug in Cygwin. I ran your testcase and I can reproduce the behaviour on 1.5.25-11. The problem does not occur in current CVS, though, so it seems it has been fixed in CVS at one point. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/