That error message usually means that memory which was allocated by one thread was freed by another thread. This usually occurs if an XS-based module is not written to be thread-safe, or is buggy. Less commonly in recent perls, it may indicate a bug in perl itself.
The usual way to debug such things is to set a breakpoint at the place in the src where the error is is tested for and raised, to see what address is being freed, and by what. Then re-run with a conditiomnal breakpoint set in the allocation code to see where that address is allocated.
Run gdb with PERL_HASH_SEED=0 to get consistent results between runs.
Dave.
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.