Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-ID: <000801c30db9$8ff11c40$2e5986d9@ellixia>
From: "Elfyn McBratney" <elfyn-cygwin AT exposure DOT org DOT uk>
To: "cygwin" <cygwin AT cygwin DOT com>, "Michael Lemke" <lemkemch AT t-online DOT de>
References: <UTZVTO32ZY1XWRZV62ZT843WWUQNWUNH DOT 3ead71ec AT micha>
Subject: Re: Perl instabilities
Date: Mon, 28 Apr 2003 19:30:47 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

> >If you're setting it from bash, make sure to escape the backslashes (or
> >use forward slashes).  You might also have to set error_start before
> >starting any Cygwin processes (if I'm wrong, someone please correct
me)...
>
> Thanks for the warning, Igor.  I set it in the .cmd file which starts my
cygwin.
> To make sure I just ran a test case by writing a program that crashes.
dumper started
> as supposed to.  But it wrote an empty core file.... :-(
>
> Anyway, what next to try with perl?  Could it have anything to do with
threads?
> I just had the problem when I tried to build perl on VMS.  Threads and
64bit stuff
> wouldn't work.  Just a thought.

Just a WAG, maybe it's down to the 64-int support. Perhaps re-building from
source without 64-int might do something...

Elfyn


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