RE: XFree leaking memory?

[Jean-Claude Gervais <jc dot gervais at videotron dot ca>]

Thanks Ralf,

	There is also this tool -
http://devel-home.kde.org/~sewardj/

	Not sure if it can be used on Cygwin, but I think it might.

	Anyhow, I'll run some tests and report back.



-----Original Message-----
From: cygwin-xfree-owner@cygwin.com [mailto:cygwin-xfree-owner@cygwin.com]On
Behalf Of Ralf Habacker
Sent: Tuesday, November 05, 2002 3:18 PM
To: cygwin-xfree@cygwin.com
Subject: RE: XFree leaking memory?

> In other words, it might not be able to follow NEW or MALLOC, because the
> object format might be too different.
>
Try the mem_watch tool in the kde-cygwin cvs area
http://sourceforge.net/cvs/?group_id=27249, which hooks any memory relating
call.

$ less README
Memory Watcher
==============

This is a little library for tracing memory related api calls on win32 using
gcc.

Features:
- detection of unfree'd memory regions
- traces each malloc(), calloc(), realloc() and free() call
- collects size and addresses of allocated area
- runtime switchable logging support of hooked function

See INSTALL for installation hints.

The only thing you have to do is to adding a call after main() and perhaps
one
call for printing the results at the end of main().

Try
$cvs -d:pserver:anonymous@cvs.kde-cygwin.sourceforge.net:/cvsroot/kde-cygwin
login
<empty password>
$cvs -z3 -d:pserver:anonymous@cvs.kde-cygwin.sourceforge.net:/cvsroot/kde-cy
gwin
co tools/mem_watch
$ make
$ make check
$ test.exe