|
From: Brendan D. <bre...@pe...> - 2006-03-01 00:11:03
|
[snip] > As the FAQ says, if it is a heap block overrun problem Memcheck should > report some invalid write before the crash. You haven't said if it does. > >> Are there any _particular_ symptoms or patterns in the code that I >> should be looking for to diagnose this problem? > > Heap block overruns. > > In short, what the FAQ says. > > Nick There were invalid reads and writes prior to that point. Are there things I can do to try to protect the stack and the heap (like passing -fmud-flapth -lmudflap to GCC as I'm compiling and linking) inside Valgrind? Or at least have things blow up closer to where the actual source of the bug is? Without having access to the code which causes these issues, I'm quickly running out of good ideas -- any suggestions would be greatly appreciated. Thanks, Brendan. -- Brendan Drew Research Scientist PercepTek, Inc. 12395 North Mead Way Littleton, CO 80125 Tel: 720-344-1037 x 126 Fax: 720-344-2360 |