It means that if you have a program that calls malloc() and it gets interrupted for another task that calls malloc(), there's no guarantee that the original call won't be thrashed by the second. An interesting link about glibc is here.

Effectively, this comes up in Perl when you write your own signal handlers. As they're invoked via signals (interrupting the normal flow of operation), there's a possibility that another signal could come in as you are trying to deal with the first.

That's still not a very effective explanation. Okay, think of it like spinning plates on sticks. You'll be better at it when you only have one to do. If you get interrupted while spinning one to go do another, you might have a crash a few moments later.

(Get around this by doing as little as possible in your signal handlers.)

In reply to Re: Malloc is not reentrant? by chromatic
in thread Malloc is not reentrant? by floopy

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.