UNITCHECK and require

[Adrien BARREAU]

Hi all.

I just found a way to kill my Perl and I don't find anything about that.
Here it is:

=====
$ perl --version

This is perl, v5.10.1 (*) built for x86_64-linux-gnu-thread-multi
(with 61 registered patches, see perl -V for more detail)


$ cat death.pm
package death;
UNITCHECK { require stuff; }
1;

$ cat stuff.pm
package stuff;
1;

$ perl -e 'use death; print "ok\n";'
$ perl -e 'require death; print "ok\n";'
Segmentation fault
=====

Well, perhaps trying to require something in a UNITCHECK is not a good idea.
But still, segfault...

That's strange that the "use" version does not actually display anything
at all, although that seems to be quite random.

Does anybody have any piece of information about that?


Adrien.

 

[Adrien BARREAU]

For the record, I suspect this is the same bug as
https://rt.perl.org/rt3/Public/Bug/Display.html?id=70614 . It doesn't
look the same until you remember that 'require' is really just a
variation of string-eval.

Ben

I can reproduce something strange behaviours like that:

=====
$ cat death.pm
package death;
UNITCHECK { eval '' }
1;

$ perl -e 'require death; print "ok\n"'
$
# ---

$ cat death.pm
package death;
UNITCHECK { eval {} }
1;

$ perl -e 'require death; print "ok\n"'
ok
=====

No segfault, but nothing either with an eval-string.
Strange...

Adrien.