Sender: amwalker AT gate DOT net
Message-ID: <370AB0A3.FEEBB10E@gate.net>
Date: Wed, 07 Apr 1999 01:10:59 +0000
From: Aaron Walker <amwalker AT gate DOT net>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.0.36 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: djgpp AT delorie DOT com
Subject: Re: ANNOUNCE: YAMD malloc debugger v0.2
References: <199904040340 DOT WAA02622 AT delorie DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com

Hello,

I am very interested in this...  I downloaded, compiled, and attempted to
use it.
I had already compiled by program with -g and all the required stuff, so
I just ran
run-yamd.  It printed out about 10megs worth.  Does it log every malloc
call, successfull or not, or just the ones that have multiple frees,
memory leaks, etc.?

I am writing a program with the GTK+ graphics lib in linux, and using
wrappers (g_malloc and g_free).
I'm guessing it should still work...

the problem is, I don't know if GTK takes care of freeing the memory or
not, so I need a malloc debugger such as yamd or electric fence to see
whether or not I need to free that memory.  The only thing I've used
malloc on is a structure.  ElectricFence returned no errors, so I assume
everything is ok.

Anyways, thanks very much for your help, and keep up the good work on
yamd.

Aaron

Nate Eldredge wrote:

> This is to announce the upload of version 0.2 of YAMD (Yet Another
> Malloc Debugger).  It can be fetched from:
>
> http://www.cartsys.com/eldredge/n/yamd/
>
> YAMD is a package for finding bugs related to dynamic memory allocation
> (pointer overruns, memory leaks, etc).  Among its special features:
>
> * Paging mechanisms are used to trap illegal memory accesses.  This
> means that reads as well as writes can be caught, and are caught
> immediately, rather than at some later time.
>
> * All operations are logged with a traceback to aid in finding why some
> allocation or other went awry.
>
> * No changes to your source are required to use YAMD.
>
> * Everything else you'd expect from a malloc debugger; checking of
> "obvious" errors like multiple freeing, etc.
>
> YAMD also works under Linux, and in fact supports some additional
> features there.
>
> Some restrictions do apply:
>
> - Several DPMI 1.0 features are essential to the way YAMD works;
> therefore, **it will only work under plain DOS with CWSDPMI as the DPMI
> server**.
>
> - A fairly large amount of swap space is recommended.
>
> Copying policy is GPL.
>
> Please check it out, and report any successes/failures/bugs to me:
> <nate AT cartsys DOT com>.
> --
>
> Nate Eldredge
> nate AT cartsys DOT com

--
Aaron Walker
amwalker AT gate DOT net
http://iconmedia.com/aaron