X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-497711.8 required=5.0 tests=AWL,BAYES_00
X-Spam-Check-By:	sourceware.org
X-MDAV-Processed:	mail1.multiplay.co.uk, Thu, 07 Jan 2010 21:53:05 +0000
X-Spam-Processed:	mail1.multiplay.co.uk, Thu, 07 Jan 2010 21:53:05 +0000 (not processed: message from trusted or authenticated source)
X-MDRemoteIP:	213.123.247.160
X-Return-Path:	prvs=1623dfa582=killing AT multiplay DOT co DOT uk
X-Envelope-From:	killing AT multiplay DOT co DOT uk
X-MDaemon-Deliver-To:	cygwin AT cygwin DOT com
Message-ID:	<DCF1A1122772481793DC3902EA242819@multiplay.co.uk>
From:	"Steven Hartland" <killing AT multiplay DOT co DOT uk>
To:	"Cygwin List" <cygwin AT cygwin DOT com>
References:	<19C1823A54BB4C058061C783D86F41F8 AT multiplay DOT co DOT uk>
Subject:	Re: cygwin, perl or DBI seriously broken in 1.7.1?
Date:	Thu, 7 Jan 2010 21:52:57 -0000
MIME-Version:	1.0
X-IsSubscribed:	yes
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

Been trying a few things and going back from perl 5.10.1-2 to
perl 5.10.1-1 fixes the issue, or at least I can now no longer
reproduce the problem readily.

Looking at the differences seem to be the change in flags from
"-Dmad=y" -> "-Doptimize=-O3" so we could be looking at a
compiler bug?

One thing for sure though 5.10.1-2 is not reliable here.

    Regards
    Steve


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