|
From: Nicholas N. <nj...@cs...> - 2005-03-04 05:34:26
|
CVS commit by nethercote: update M +6 -5 valgrind-quick-start 1.5 --- devel-home/valgrind/valgrind-quick-start #1.4:1.5 @@ -10,5 +10,7 @@ What follows is the minimum information you need to start detecting memory -errors in your program with Memcheck. +errors in your program with Memcheck. Note that this guide applies to +Valgrind version 2.4.0; some of the information is not quite right for +earlier versions. @@ -25,9 +27,8 @@ Use this command line: - valgrind --tool=memcheck --num-callers=40 --leak-check=yes myprog arg1 arg2 + valgrind --leak-check=yes myprog arg1 arg2 -The --tool option invokes Memcheck. The --num-callers option asks for big -stack traces, which make error messages more informative. The --leak-check -option turns on the memory leak detector. +Memcheck is the default tool. The --leak-check option turns on the memory +leak detector. Your program will run much slower (eg. 20 to 30 times) than normal, and use |