Thanks for the hint. I've tried the Perl debugger and found the following:

It is crashing in the module Exporter, line 64:

[31499->31499] DB<1> Exporter::import(/export/packages/perl-5.12.3/li +b/5.12.3/Exporter.pm:64): 64: *{"$callpkg\::$_"} = \&{"$pkg\::$_"} foreach @_;
where the variables are:
$callpkg = "Module::Runtime" @_ = ("is_string") $_ = "is_string" $pkg = "Params::Classify"
When I tried to feed the debugger with this:
&{"$pkg\::$_"}
the debugger crashed. So there is probably something bad going on in Params::Classify. The generated core dump shows, that it crashed in lib/params/Classify.xs:635. The backtrace is very high and starts like this:
... #87243 0x00007fd820981b7a in myck_entersub (my_perl=0x2143000, op=0x26 +0b250) at lib/Params/Classify.xs:635 #87244 0x00007fd820981b7a in myck_entersub (my_perl=0x2143000, op=0x26 +0b250) at lib/Params/Classify.xs:635 #87245 0x00007fd820981b7a in myck_entersub (my_perl=0x2143000, op=0x26 +0b250) at lib/Params/Classify.xs:635 #87246 0x00007fd820981b7a in myck_entersub (my_perl=0x2143000, op=0x26 +0b250) at lib/Params/Classify.xs:635 #87247 0x00007fd826cae142 in Perl_convert (my_perl=0x2143000, type=173 +, flags=192, o=0x260b250) at op.c:2652 #87248 0x00007fd826cb351c in Perl_utilize (my_perl=0x2143000, aver=1, +floor=147, version=0x0, idop=0x2617d20, arg=0x264e210) at op.c:3979 #87249 0x00007fd826d4d17c in Perl_yyparse (my_perl=0x2143000) at perly +.y:674 #87250 0x00007fd826ef2d6d in S_doeval (my_perl=0x2143000, gimme=2, sta +rtop=0x0, outside=0x0, seq=2054) at pp_ctl.c:3112 #87251 0x00007fd826efa35e in Perl_pp_require (my_perl=0x2143000) at pp +_ctl.c:3690 #87252 0x00007fd826da5fc8 in Perl_runops_debug (my_perl=0x2143000) at +dump.c:2049 #87253 0x00007fd826cdadb6 in Perl_eval_sv (my_perl=0x2143000, sv=0x216 +0e28, flags=4) at perl.c:2705 #87254 0x0000000000401a47 in perl_load_module_1 () #87255 0x00000000004040f9 in main ()
The function "myck_entersub" is calling itself ad infinitum, which is not good. My guess is there's something wrong with Classify.xs. Unfortunately, I don't know how to fix it. Do you have any ideas?

In reply to Re^2: Multiple perl interpreters and Module::Runtime (-d) by daneus
in thread Multiple perl interpreters and Module::Runtime by daneus

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.