|
From: Nicholas N. <nj...@cs...> - 2005-03-01 02:57:35
|
CVS commit by nethercote: wibble M +4 -4 valgrind-quick-start 1.2 --- devel-home/valgrind/valgrind-quick-start #1.1:1.2 @@ -89,8 +89,8 @@ Memory leak messages look like this: -==19182== 40 bytes in 1 blocks are definitely lost in loss record 1 of 1 -==19182== at 0x1B8FF5CD: malloc (vg_replace_malloc.c:130) -==19182== by 0x8048385: f (a.c:7) -==19182== by 0x80483AB: main (a.c:14) + ==19182== 40 bytes in 1 blocks are definitely lost in loss record 1 of 1 + ==19182== at 0x1B8FF5CD: malloc (vg_replace_malloc.c:130) + ==19182== by 0x8048385: f (a.c:7) + ==19182== by 0x80483AB: main (a.c:14) The stack trace tells you where the leaked memory was allocated. Memcheck |