X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 15 Jul 2009 19:29:57 +0200 From: Corinna Vinschen 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: <20090715172957.GV27613@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20090714200631 DOT GP27613 AT calimero DOT vinschen DOT de> <20090714205617 DOT GA12534 AT ednor DOT casa DOT cgf DOT cx> <8541BCA91FF64580AA7A8065FBF9C938 AT multiplay DOT co DOT uk> <39B3B148DA514671BB2E1AE46946169C AT multiplay DOT co DOT uk> <20090715000331 DOT GA5635 AT ednor DOT casa DOT cgf DOT cx> <6D01817BC10A4430AFE7A590CC935C09 AT multiplay DOT co DOT uk> <20090715152139 DOT GA694 AT calimero DOT vinschen DOT de> <20090715162317 DOT GM14502 AT ednor DOT casa DOT cgf DOT cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090715162317.GM14502@ednor.casa.cgf.cx> User-Agent: Mutt/1.5.19 (2009-02-20) 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 Jul 15 12:23, Christopher Faylor wrote: > On Wed, Jul 15, 2009 at 05:21:39PM +0200, Corinna Vinschen wrote: > >==== SNIP ==== > >#include > >#include > >#include > > > >pthread_attr_t attr; > > > >void *thr (void *arg) > >{ > > printf ("I'm a thread\n"); > > return NULL; > >} > > > >int main() > >{ > > pthread_t t; > > int i, r; > > void *ret; > > > > fprintf (stderr, "Testing threads...\n"); > > i = pthread_attr_init (&attr); > > printf ("i = %d\n", i); > > r = pthread_create (&t, &attr, thr, NULL); > > if (r) > > fprintf (stderr, "pthread_create: %d %s\n", errno, strerror (errno)); > > else > > pthread_join (t, &ret); > > fprintf (stderr, "Testing done\n"); > > return 0; > >} > >==== SNAP ==== > > I can't try this right now myself but what about trying various settings > for a SIGSEGV signal handler? No SIGSEGV setting has any visible effect. In the Perl testcase _cygtls::handle_exceptions is just not called, in the C testcase it's always called. 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