This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Perl instabilities
- 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>
- Date: Mon, 28 Apr 2003 19:30:47 +0100
- Subject: Re: Perl instabilities
- References: <UTZVTO32ZY1XWRZV62ZT843WWUQNWUNH.3ead71ec@micha>
> >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/