|
From: Dennis L. <pla...@tz...> - 2005-08-08 17:30:36
|
Hi, unfortunately valgrind cannot catch all errors, as described in some FAQs, some (quite rare) cases are missed. Although the address in your glibc message suggests that it is a programming error, maybe you have temperature problems (as you described). To check this, run memtest86+ for testing your memory and prime95 (from mersennne.org) for cpu testing (torture test). If both dont return errors, you are a bit on your own with the classical debugging techniques (gdb, examining core dums, running program with MALLOC_CHECK_ set etc.) greets Dennis Am Montag, den 08.08.2005, 17:48 +0100 schrieb Richard Corden: > 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 > -- Dennis Lubert <pla...@tz...> |