X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By:	sourceware.org
Message-ID:	<4A608C72.2010504@gmail.com>
Date:	Fri, 17 Jul 2009 15:36:34 +0100
From:	Dave Korn <dave DOT korn DOT cygwin AT googlemail DOT com>
User-Agent:	Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version:	1.0
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 )
References:	<20090715185636 DOT GA16211 AT ednor DOT casa DOT cgf DOT cx> <4A5E2ED6 DOT 3070502 AT gmail DOT com> <20090715194539 DOT GZ27613 AT calimero DOT vinschen DOT de> <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> <loom DOT 20090717T140900-805 AT post DOT gmane DOT org>
In-Reply-To:	<loom.20090717T140900-805@post.gmane.org>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Eric Blake wrote:

> static int (*cygwin_exception_handler) (EXCEPTION_RECORD *, void *, CONTEXT *, 
> void *);
> 
> /* Our exception handler.  */
> static int
> libsigsegv_exception_handler (EXCEPTION_RECORD *exception, void *frame, CONTEXT 
> *context, void *dispatch)
> {
>   EXCEPTION_POINTERS ExceptionInfo;
>   ExceptionInfo.ExceptionRecord = exception;
>   ExceptionInfo.ContextRecord = context;
>   if (main_exception_filter (&ExceptionInfo) == EXCEPTION_CONTINUE_SEARCH)
>     return cygwin_exception_handler (exception, frame, context, dispatch);
>   else
>     return 0;
> }

  That looks fairly robust to me, shouldn't give us any problems.  Question
is, what does the code that hooks and unhooks the exception handler look like,
and where does it get called from?

> [m4 wouldn't need to use libsigsegv if cygwin provided sigaltstack, but that's 
> an entirely different can of worms.]

  Nuns!  Nuns!  Reverse!  Reverse!  Reverse!

    cheers,
      DaveK

--
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

- Raw text -