What value did you give to the MALLOC_CHECK_ ? Try assigning e.g. MALLOC_CHECK_=3, so that SIGABRT is raised. You should get a stack trace in gdb regardless of debugging symbols. ("where").

Do I read this correctly: in valgrind your program runs successfully to completion? In other words, a heisenbug? Valgrind has some options to play with. You can try --malloc-fill=.. and --free-fill=.. to poison the chunks.

Are you sure your modules are correctly linked? Valgrind by default only hooks dynamically linked calls (to libc.so).

Do you make use of threads?

In reply to Re: *** glibc detected *** perl: corrupted double-linked list by Anonymous Monk
in thread (resolved) *** glibc detected *** perl: corrupted double-linked list by tj_thompson

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.