���� ���, 9 ������� 2002, 19:36, voguemaster ���:
> >There are plenty of open source utilities: memory patrol, electric fence,
> > checker - just to name a few. I don't have time to check every one of
> > them. What you can propose ?
>
> I've had good experience with DMALLOC and a bit of electric fence. I
> haven't been able to find a VERY GOOD tool for multithreaded appications
> :-\
>
> Can you elaborate a bit more on your problem ? Are you absolutely sure it's
> related to memory leaks ? could it be something else (such as heap
> corruption) ??
>
> Have you tried wrapping around malloc()/free() calls and print some debug
> information ? After the program stops you might parse the info and look for
> indescrepencies.... just a thought..
In the open source project I'm working on - Kannel, we have a malloc()/free()
wrapper which reports memory leaks and keeps track of the function who owns
each memory block. it's not fool proof, but at times have proven valuable at
tracking down memory problems.
--
Oded
::..
WWW is the MS-DOS of hypertext systems...
-- Erik Naggum
================================================================To unsubscribe, send
mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
