Hi, I've been having an odd experience lately with a program I code for a Linux architecture. When allocating memory via the calloc function it for some reason seems to randomly fail when calloc calls mallopt. Most often when I view the core dump it shows in the backtrack the call to the calloc function in lib.libc.so.6 then two or three calls to the mallopt function in lib.libc.so.6 and occassionally it'll then show abort() raise() kill() calls and I'm not sure why. It happens randomly and I was wondering if anyone could shed some light on the situtation. Also the Glibc is version 2.3.4 not sure if that helps or not...

check your code .. it's not system that's random .. something in your code is causing it.
good practice to print errno after system calls.

It truly was random, I modified the code so that instead of using calloc it uses malloc and modified the macro so it was stuck in a for loop until it got a valid chunk of memory and the program hasn't locked up from it and it hasn't crashed since. Either way the whole thing is odd since that code hadn't changed for 6 years before it started doing it.