http://qs321.pair.com?node_id=666618


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

I can report that after upgrading to Safe 2.14 that the problem still exists, as per my previous description.
  • Comment on Re^2: What Just Happened to my CPAN Shell?

Replies are listed 'Best First'.
Re^3: What Just Happened to my CPAN Shell?
by haoess (Curate) on Feb 06, 2008 at 17:45 UTC

    Latest (the fixed one) Safe is 2.15 (should hit your favourite CPAN mirror soon).

    -- Frank

      I can report that after upgrade to Safe 2.15 that the problem still exists.
        I can report that after upgrade to Safe 2.15 that the problem still exists.

        Nice. Your perl is 5.8.8? Could you please try the following test script?

        use warnings; use strict; use Safe; use version; my $comp = Safe->new; # never using it! my $code = <<'EOT'; use version; qv('3.0.17'); EOT my $ret = eval($code); print "$ret"; # should stringify the version

        On my system with Safe 2.14 the script produces a SEGV:

        $ perl test.pl Use of inherited AUTOLOAD for non-method version::(""() is deprecated +at test.pl line 13. Segmentation fault

        But with Safe 2.15 it runs fine.

        -- Frank