|
From: Nalin K. J. <na...@no...> - 2007-09-06 08:20:50
|
Hi, We are upgrading from Valgrind 2.0.0 to Valgrind 3.2.3. We found some of the definitely lost blocks which are getting reported by Valgrind 2.0.0 are now not getting reported with 3.2.3. The valgrind log file has reduces to about one tenth of the original size. VALGRIND_OPTS for 2.0.0 "--leak-check=yes --num-callers=18 --leak-resolution=high --logfile=valgrind200_.log" VALGRIND_OPTS for 3.2.3 "--leak-check=full --num-callers=18 --leak-resolution=high --log-file=valgrind.log" We are getting following error only with 3.2.3 ==15464== Syscall param write(buf) points to uninitialised byte(s) ==15464== at 0x474428B: write (in /lib/i686/libpthread-0.10.so) ==15464== by 0x47B43D2: exit (in /lib/i686/libc-2.3.2.so) ==15464== by 0x479EBC1: (below main) (in /lib/i686/libc-2.3.2.so) ==15464== Address 0xBEFF8BBC is on thread 1's stack Thanks Nalin |