From b1db9dbb1607f6ffbea1a0f628739ae993b8aeb1 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Sun, 29 Oct 2006 23:00:52 +0000 Subject: corrected how tests/memanalyze.pl is used --- lib/README.memoryleak | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/lib/README.memoryleak b/lib/README.memoryleak index 552836385..8aa6094fd 100644 --- a/lib/README.memoryleak +++ b/lib/README.memoryleak @@ -29,7 +29,7 @@ Modify Your Application Add a line in your application code: - curl_memdebug("filename"); + curl_memdebug("dump"); This will make the malloc debug system output a full trace of all resource using functions to the given file name. Make sure you rebuild your program @@ -45,9 +45,9 @@ Run Your Application Analyze the Flow - Use the tests/memanalyze.pl perl script to analyze the memdump file: + Use the tests/memanalyze.pl perl script to analyze the dump file: - tests/memanalyze.pl < memdump + tests/memanalyze.pl dump This now outputs a report on what resources that were allocated but never freed etc. This report is very fine for posting to the list! -- cgit v1.2.3