From: scott <listS+cygwin@niss.com>
To: cygwin@cygwin.com, Corinna Vinschen <corinna-cygwin@cygwin.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
Date: Thu, 08 Mar 2012 00:21:00 -0000 [thread overview]
Message-ID: <BD.FA.05889.F6BF75F4@hrndva-omtalb.mail.rr.com> (raw)
In-Reply-To: <20120307155436.GK5159@calimero.vinschen.de>
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
next prev parent reply other threads:[~2012-03-08 0:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 15:31 Kelly, Brian
[not found] ` <50BA2F81CF76F7438BD87069FCFD413501BB608EE2@cexchmb1.bcbsa.com>
2012-03-07 15:53 ` Kelly, Brian
2012-03-07 15:55 ` Corinna Vinschen
2012-03-08 0:21 ` scott [this message]
2012-03-08 5:08 ` marco atzeri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BD.FA.05889.F6BF75F4@hrndva-omtalb.mail.rr.com \
--to=lists+cygwin@niss.com \
--cc=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).