|
From: Richard C. <ric...@pr...> - 2005-08-08 16:48:52
|
Hi, One of our tools fails some tests on one of our machines. The failures are consistent and reproducible, they are seg 11s, and in some cases I get a message from glibc. *** glibc detected *** free(): invalid pointer: 0x082587f4 *** These messages always have the same memory address. The interesting thing is that when I run the same test with valgrind, I don't get any failures, and the tools pass the test as expected. Initially 'valgrind' found a 'memcpy' with overlapping memory which is now fixed but other than that there were no other issues when using --tool=memcheck. The machine is relatively new (Intel Zeon hyper threading P4 3.2GHz) and I have had problems keeping it cool, I do get a lot of messages from syslogd about passing temperature threshold. I need to find out if it is the overheating of the CPU or ?something else? which causes the failure? My question is, what could valgrind be doing that might stop the problem from occurring? I've been running using --tool=memcheck, should I try something else? Regards, Richard -- Richard Corden |