On Wed, 8 Jan 2003, Henke, Markus wrote:

> i've just discovered the "curl_memdebug()"-feature and begun to play
> arround with it (Win32) according to the doc "README.memoryleak".

Just be aware of that I don't know if anyone ever has done this on Windows
before. I can't say I know any reason why it would work differently, but you
never know... :-)

> But it seems to me that the analyzer "memanalyze.pl" won't generate any
> output. Well, of course that's because libcurl hasn't any memory leak... =]

So, do you get a file output that you can browse manually at least?

> But i've commented out "curl_easy_cleanup" in a testapp and / or wrecked
> the memdump file of the testapp to see how it would be if there's a leak,
> still "memanalyze.pl" does nothing...

--- testfile start---
MEM url.c:241 malloc(67260) = 0x8104304
MEM url.c:250 malloc(256) = 0x81149d4
--- testfile end ---

$ memanalyze.pl < testfile
Leak detected: memory still allocated: 67516 bytes
At 8104304, there's 67260 bytes.
 allocated by url.c:241
At 81149d4, there's 256 bytes.
 allocated by url.c:250

If this isn't shown, can you post your memdebug dump here and let me try it
and see if I can figure out why memanalyze fails?

-- 
 Daniel Stenberg -- curl, cURL, Curl, CURL. Groks URLs.
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com