|
From: <sv...@va...> - 2005-12-19 19:38:52
|
Author: njn Date: 2005-12-19 19:38:43 +0000 (Mon, 19 Dec 2005) New Revision: 5381 Log: update (r5380 from trunk) Modified: branches/VALGRIND_3_1_BRANCH/docs/xml/FAQ.xml Modified: branches/VALGRIND_3_1_BRANCH/docs/xml/FAQ.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- branches/VALGRIND_3_1_BRANCH/docs/xml/FAQ.xml 2005-12-19 19:38:02 UTC= (rev 5380) +++ branches/VALGRIND_3_1_BRANCH/docs/xml/FAQ.xml 2005-12-19 19:38:43 UTC= (rev 5381) @@ -410,7 +410,7 @@ functions, such as malloc(), with their own versions. A key indicator= of this is if Memcheck says: <programlisting> -No malloc'd blocks -- no leaks are possible +All heap blocks were freed -- no leaks are possible </programlisting> when you know your program calls malloc(). The workaround is to avoid statically linking your program.</para> |