X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Sat, 21 Aug 2010 11:37:03 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Bug in fork() while in a thread Message-ID: <20100821093703.GR11340@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20100815185353.GA26993@ednor.casa.cgf.cx> <20100816090552.GA11340@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) 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 Aug 21 08:50, Jason Curl wrote: > Open Group Posix.1c-2004 mentions only a "signal stack" doesn't need to be > copied for XSI. > > Linux & FreeBSD 7.0 work OK. QNX641 returns ENOSYS if it even sniffs a thread > call. I haven't tested Solaris Sparc. > > Which standard is Cygwin "closest" to, that I can use as a reference when I > trip up on similar problems? I have the hint the SuSv4 implementation of Posix. We're trying for Linux in the first place, with POSIX/SusV4 as fallback. Due to a lot of Windows quirks and the limited number of Cygwin "kernel' hackers, it's not exactly simple. 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