X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE
X-Spam-Check-By:	sourceware.org
X-Authority-Analysis:	v=2.0 cv=M9vP2lMs c=1 sm=0 a=I35YE/31jyzKHWIan582YQ==:17 a=gq4V9bB94NwA:10 a=mN5dYfLZerQA:10 a=nZcEhgTK-QsA:10 a=TK8LywrzKogA:10 a=kj9zAlcOel0A:10 a=WU00Sw-YvtcXw7FIpg4A:9 a=CjuIK1q_8ugA:10 a=I35YE/31jyzKHWIan582YQ==:117
To:	cygwin AT cygwin DOT com, Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
Message-ID:	<BD.FA.05889.F6BF75F4@hrndva-omtalb.mail.rr.com>
From:	scott <listS+cygwin AT niss DOT com>
Subject:	Re: Both versions of Perl (5.10 and 5.14) DLL collision on XP Pro, rebase does not work - serious problem with latest Cygwin base Release - 1.7.11-1
In-reply-to:	<20120307155436.GK5159@calimero.vinschen.de>
References:	<50BA2F81CF76F7438BD87069FCFD413501BB608EE1 AT cexchmb1 DOT bcbsa DOT com> <20120307155436 DOT GK5159 AT calimero DOT vinschen DOT de>
Comments:	In-reply-to Corinna Vinschen <corinna-cygwin AT cygwin DOT com> message dated "Wed, 07 Mar 2012 16:54:36 +0100."
MIME-Version:	1.0
Date:	Wed, 07 Mar 2012 18:21:03 -0600
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On Wed, 7 Mar 2012 16:54:36 +0100, Corinna Vinschen wrote:
> On Mar  7 09:30, Kelly, Brian wrote:
> > On two systems I tested this on, the latest cygwin base release breaks
> > both releases of Perl. The problem appears to be some type of DLL
> > collision with some types of compiled Perl modules on Windows XP
> > Professional. Below is a simple example using the Data::Dump::Streamer
> > module:
> > 
> > 
> > use Data::Dump::Streamer;
> > my $out=`ls`;
> > print "OUT=$out\n";
> > 
> > 
> > When run, it produces the following output:
> > 
> > $ perl test.pl
> >       8 [main] perl 3692 child_copy: loaded dll data write copy failed, 0x57573000..0x575733E0, done 0, windows pid 23
> 20, Win32 error 487
> > 
> > 
> > If you comment out the module, the backtick `ls` and print run fine.
> > If you comment out the backtick line, the module loads fine. But
> > together, I see the problem.
> > 
> > I have already attempted to run rebaseall and perlrebase (multiple
> > times in fact), but these do not correct the problem. When I roll back
> > to release 1.7.10-1, (with *NO* other changes), the problem goes away.
> 
> Did you also rebase the DLL providing Data::Dump::Streamer?  I'm not
> fluent in perl so I don't know how to get this DLL.  The above is
> definitely a collision problem, but it may be persistent for you because
> the self-built(?) DLL is never taken into account when rebasing.

	When I run (rebaseall -v) it confirms that the rebaseall
	successfully finds all the perl module DLL's. Those will be for
	modules that include C code which is locally compiled.

		Scott

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