Message from discussion Cygwin problems are GC not ICU (was Re: Cygwin issues may not be ICU related)
Mailing-List: contact perl6-internals-h...@perl.org; run by ezmlm
Delivered-To: mailing list perl6-intern...@perl.org
Delivered-To: moderator for perl6-intern...@perl.org
Received: (qmail 65914 invoked from network); 5 May 2004 12:38:17 -0000
Received: from x1.develooper.com (22.214.171.124)
by onion.develooper.com with SMTP; 5 May 2004 12:38:17 -0000
Received: (qmail 24076 invoked by uid 225); 5 May 2004 12:38:17 -0000
Received: (qmail 24066 invoked by alias); 5 May 2004 12:38:16 -0000
X-Spam-Status: No, hits=3.0 required=7.0
Received: from web60807.mail.yahoo.com (HELO web60807.mail.yahoo.com) (126.96.36.199)
by la.mx.develooper.com (qpsmtpd/0.27.1) with SMTP; Wed, 05 May 2004 05:38:15 -0700
Received: from [188.8.131.52] by web60807.mail.yahoo.com via HTTP; Wed, 05 May 2004 05:38:11 PDT
Date: Wed, 5 May 2004 05:38:11 -0700 (PDT)
Subject: Cygwin problems are GC not ICU (was Re: Cygwin issues may not be ICU related)
Cc: Jeff Clites <jcli...@mac.com>
Content-Type: text/plain; charset=us-ascii
X-Spam-Rating: onion.develooper.com 1.6.2 0/1000/N
From: limbic_region_2...@yahoo.com (Joshua Gatcomb)
--- Jeff Clites <jcli...@mac.com> wrote:
> If you run it in a debugger (gdb or whatever), you
> should be able to
> see where it's crashing.
Ok, after spending about 5 minutes figuring out what
gdb was and how to use it (did I mention I was
clueless) it looks like it isn't ICU at all!!!!
Program received signal SIGSEGV, Segmentation fault.
0x00419f6c in new_pmc_header (interpreter=0x100d1d48,
flags=1024) at src/headers.c:251
Ok, so I naively tried --gc=libc and --gc=malloc and
it didn't seem to help.
So in retrospect, it appears that there are a number
of ways getting ICU playing nice on Cygwin but until
this other issue is resolved they don't matter. If
anyone is interested in a complete list of recipes I
have used then let me know.
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs