|
From: Michael W. <mic...@gm...> - 2008-07-11 14:22:24
|
> Recently, we've been seeing messages like "glibc detected: corrupted > double-linked list" followed by a crash. Memcheck reported absolutely no > errors. I've actually had the same problem, myself. In my case, it was an unsigned char array that was being c'allocted, passed through some functions, and modified along the way via pointer dereferencing and direct incrementation (ie: *chararray++ = '%c' ) somehow this caused the above error, most often I believe if/when the array was written past (buffer overflow) I was able to get rid of the problem by removing the c'alloc and re-engineering some code, but the general idea yah, same bug, no error in valgrind of any use... it did point me at a line of code involved in the frame-stack that triggered the error, but nothing more than a single line (no called from, etc.) |