I've finally found the answer. I set the MALLOC_CHECK_ environment variable to 0 in my startup script to resolve the issue.

MALLOC_CHECK_=0

According to the GNU C Library Reference Manual, MALLOC_CHECK_ is used to check for and guard against bugs in the use of malloc, realloc and free. If MALLOC_CHECK_ is set to 0, any detected heap corruption is silently ignored; if set to 1, a diagnostic is printed on stderr; if set to 2, abort is called immediately.

No comments:

Post a Comment

Subscribe to fahd.blog

Hi, I'm Fahd, a software developer at an investment bank in London. I am passionate about technology and work mainly with open source software, specialising in Java applications and Unix-based operating systems.

This blog is a place for me to share useful code snippets to solve problems that I have come across, and to write about ideas and experiences as a programmer.

All code on this blog has been written by me, unless stated otherwise, and you are free to use, share and adapt it for any purpose, under the terms of the GNU General Public License.

I love hearing back from my readers, so please feel free to leave comments! Thanks for reading and happy programming :-)