in reply to Re^5: What Just Happened to my CPAN Shell?
in thread What Just Happened to my CPAN Shell?

Yes, my perl is 5.8.8:
$ perl -v This is perl, v5.8.8 built for x86_64-linux-gnu-thread-multi [...snip...]
The test script segfaults as per your example. However:
$ perl -MSafe -e 'print $Safe::VERSION, "\n"' 2.14
I now have two's:

2.14 is in /usr/local/lib/perl/5.8.8/
2.15 is in /usr/lib/perl/5.8.8/

@INC is:
$ perl -MData::Dumper -e 'print Dumper(\@INC);' $VAR1 = [ '/etc/perl', '/usr/local/lib/perl/5.8.8', '/usr/local/share/perl/5.8.8', '/usr/lib/perl5', '/usr/share/perl5', '/usr/lib/perl/5.8', '/usr/share/perl/5.8', '/usr/local/lib/site_perl', '.' ];
I'm not sure why there is a discrepancy (no difference in Makefile.PL between the two versions), although I installed 2.14 via the CPAN shell, and 2.15 via bash.

When I upgrade the test script to 'use lib qw(/usr/lib/perl)' before 'use Safe', it does not segfault and emits:
$ perl 3.0.17

Replies are listed 'Best First'.
Re^7: What Just Happened to my CPAN Shell?
by eskwayrd (Acolyte) on Feb 06, 2008 at 23:22 UTC
    And subsequently, upgrading to Safe 2.15 via the CPAN shell causes the problem to go away, at least for two roundtrips of discovering modules with updates available, and installing the updates.