Closed GoogleCodeExporter closed 9 years ago
Unfortunately, we can't print a nice error message for every type of memory
corruption that we see -- some we can notice, but some would just be too
expensive to
check for all the time, and the detected corruption would be so far away from
where
the corruption happened, we wouldn't be able to say anything useful anyway. I
think
in general to figure out why a memory allocation operation is crashing, it's
much
more useful to use a dedicated tool, such as valgrind, or tcmalloc's
tcmalloc_debug
library.
This is almost certainly due to a memory management bug in your code, so I'm
going to
close the bug. If it turns out there's something related to tcmalloc behavior
in
here, though, feel free to reopen it.
Original comment by csilv...@gmail.com
on 30 Mar 2010 at 9:35
Original issue reported on code.google.com by
laurent....@gmail.com
on 30 Mar 2010 at 3:33