Question:

Glibc bug?

by  |  earlier

0 LIKES UnLike

Hi, I'm writing a simple program that need much memory. I allocate memory with mallocs such as this line:if ((left = malloc (sizeof (tree_node))) == NULL) fatal ("not enough memory"); But once in a while my program got a SEGV and dumped a core. I examine the core with gdb. But gdb gave me this information: Program terminated with signal 11, Segmentation fault.Cannot access memory at address 0x400fe000 #0 0x420741df in ?? ()I run the program in gdb and after a while, it cought a SEGV inside malloc!Program received signal SIGSEGV, Segmentation fault. 0x420739e5 in _int_malloc () from /lib/i686/libc.so.6But sometimes it doesn't killed by SEGV at all. Sometimes it get cought in sbrk()!Program received signal SIGSEGV, Segmentation fault. 0x420d3399 in sbrk () from /lib/i686/libc.so.6What happened to the program?

 Tags:

   Report
Please Login to view 6 answers to this question
You're reading: Glibc bug?

Question Stats

Latest activity: earlier.
This question has 6 answers.

BECOME A GUIDE

Share your knowledge and help people by answering questions.