What would really help here is to have debugging symbols on your libc.so and libperl.so, so you could do an "l" and see what exact code was being run in those crashing functions, with what values. On Debian derivatives that should be achievable by installing the appropriate packages.

A quick surmise from the first stack-trace is that Net::Curl appears to be pthreading to do its thing, then calling a Perl callback. Perl in this context may or may not be thread-safe, which would explain crashes. You haven't published an SSCCE so we can't really tell more than that. You should update to include one.

In reply to Re: POE program running into sporadic segfault by etj
in thread POE program running into sporadic segfault by pango

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.