|
From: mr e. <esn...@gm...> - 2008-01-22 17:27:54
|
Hello everybody! I'm debugging a buggy application at my job and running without valgrind, exists with: *** glibc detected *** /aplicaciones/anduin/arb.paquito/core/bin/arb: free(): invalid next size (fast): 0x08542ac0 *** Valgrind tells about several memory leaks but only shows this error: ==16767== Thread 4: ==16767== Invalid free() / delete / delete[] ==16767== at 0x402300A: free (in /usr/lib/valgrind/x86-linux/vgpreload_memcheck.so) ==16767== by 0x43A4ADD: free_mem (in /lib/libc-2.5.so) ==16767== by 0x43A4676: __libc_freeres (in /lib/libc-2.5.so) ==16767== by 0x401E216: _vgnU_freeres (in /usr/lib/valgrind/x86-linux/vgpreload_core.so) ==16767== by 0x5FCB47F: ??? ==16767== by 0x436A2ED: clone (in /lib/libc-2.5.so) ==16767== Address 0x43D9B58 is not stack'd, malloc'd or (recently) free'd That I dont understand. Is this the error that breaks the program? I'm trying to locate the point with no luck. Another thing that suprise me is that valgrind doesn't tells anything about errors like: ==25832== Invalid read of size Only tells thing about the leaked memory, but not invalid accesses. Is this normal? Any idea? Thanks a lot! |