X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Fri, 17 Jul 2009 11:44:31 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: perl threads on 2008 R2 64bit = crash ( was: perl 5.10 threads on 1.5.25 = instant crash ) Message-ID: <20090717154431.GA31572@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4A5E3F1F DOT 9040103 AT gmail DOT com> <20090716161219 DOT GP27613 AT calimero DOT vinschen DOT de> <4A5F59A1 DOT 1060902 AT gmail DOT com> <20090716195552 DOT GU27613 AT calimero DOT vinschen DOT de> <20090716211823 DOT GC22617 AT ednor DOT casa DOT cgf DOT cx> <20090717085727 DOT GW27613 AT calimero DOT vinschen DOT de> <4A607EE5 DOT 5050306 AT gmail DOT com> <20090717134114 DOT GX27613 AT calimero DOT vinschen DOT de> <4A608954 DOT 4040301 AT gmail DOT com> <20090717152920 DOT GY27613 AT calimero DOT vinschen DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090717152920.GY27613@calimero.vinschen.de> User-Agent: Mutt/1.5.20 (2009-06-14) 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 Fri, Jul 17, 2009 at 05:29:20PM +0200, Corinna Vinschen wrote: >On Jul 17 15:23, Dave Korn wrote: >> Corinna Vinschen wrote: >> > Do we have to take other handlers than the OS handlers and the Cygwin >> > handlers into account? Cygwin apps don't install SEH handlers, do >> > they? Or do C++ apps? >> >> Nope, they don't, but that will probably not be the case forever, there are >> (long-term) moves afoot to get SEH support into the compiler. However, we're >> in early startup-and-init here; we don't need to worry about what the >> application will do once it finally gets going. > >Sorry, but AFAICS we are not in early startup-and-init. The threads.dll >library is a run-time loaded DLL via dlopen due to the > > use threads; > >statement in the script. This situation can occur at any point >during the runtime of an application. Right, and I don't know how you could make the claim that Cygwin apps don't install SEH handlers. We can't possibly know how every Cygwin app does this. Obviously there's at least one app out there which has decided that it needs to use Windows-specific methods to accomplish a goal. I'm not exactly thrilled to see code which has decided to dig deep into Windows internals. That's what Cygwin is supposed to prevent. cgf -- 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