It's hard to say what goes wrong. You talk about 20k lines
of code being evalled, but you only show a few. There are
known problems with
eval, which especially arise
if there are so called "failed" evals (that don't compile)
and you have many evals. The causes are not well understood,
but a failed eval could set perl into such a state that
hundreds, if not thousands, of evals later there will be
failures, including core dumps, infite loops, and possible
other problems.
While evalling 20k lines should of course work, are you really
sure you need to eval that much? It smells very fishy.
-- Abigail
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.