Well, here are some random observations.
The backtrace in question shows that a destructor is being called during global destruction; that destructor is calling require - not illegal, but unusal; require is creating a string of some sort, and while trying to grow it, the system malloc detects some internal corruption. This usually means that something corrupted it earlier; either due to a bug in perl, or a bug in an XS module that was earlier loaded.
Building with debugging symbols will get you line numbers and function arguments, while building with Configure -DDEBUGGING may trigger an earlier assertion. But if you're on a system that supports it, you'll be best off using valgrind to see what's happening.
Finally, 5.10.1 is quite old; it may be that a bug is already fixed in 5.12.4 or 5.14.2.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||