# from John Peacock
# on Tuesday 17 April 2007 11:55 am:
>What do you have installed and what are you testing? i.e. did you
>install version-0.7201 and you are now testing Module::Build? Or you
>don't have version installed at all (which is the only way to
> correctly test the embedded code).
I can test either way. Presently, I'm at r9425 in the M::B svn with a
version-0.7201 tarball and -I switches. The segfault seems to come
from stringifying a MB::Version which was created from a real
version.pm object:
use warnings;
use strict;
use version;
use Module::Build::Version;
my $v = qv(0.0.1);
print "v: $v\n";
my $v2 = Module::Build::Version->new($v);
print "made a ", ref($v2), "\n";
print "now we segfault:\n";
print $v2;
See M::B::ModuleInfo.pm, where we harvest the version as $result and
then do this:
$result = Module::Build::Version->new($result);
Changing that to:
$result = Module::Build::Version->new(
ref($result) ? $result->{original} : $result);
Stops the segfault, but we shouldn't have to be that careful, should we?
--Eric
--
The opinions expressed in this e-mail were randomly generated by
the computer and do not necessarily reflect the views of its owner.
--Management
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
