|
From: Dennis L. <pla...@tz...> - 2004-09-13 12:57:08
|
Hello, I have now tried the 2.2 release and CVS, and after the bug with memcheck/addrcheck consuming tons of memory, I encountered another bug. Im trying to port a program to 64Bit, and before doing it, tried to fix all bugs in a 32Bit environment I can find. So I wanted to run it under valgrind, but it refused to start, with some parsing errors in the configs. This only happend when I run it under addrcheck, memcheck or massif tool, but not under cachegrind, lackey or nullgrind. Memcheck does not show any errors, except two possible memory leaks. So I suspect some bug in the part of memcheck. Unfortunately I wasnt yet able to check what exactly the difference is between the two runs, and so not able to produce any sample code that makes the error clearer. But perhaps there is also some bug known, or people working on, or some have idea where a bug could be ? Or perhaps you could give me some hints how to run valgrind to track down the problem ? greets Dennis |