Message-ID: <393F1F05.5EABD870@connect.ab.ca>
Date: Wed, 07 Jun 2000 22:20:21 -0600
From: Tom Fjellstrom <tomcf AT connect DOT ab DOT ca>
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.14-15mdk i686)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: comp.os.msdos.djgpp
Subject: ANN: XDbug 1.1
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: ppp045.connect.ab.ca
X-Trace: 7 Jun 2000 22:21:38 -0600, ppp045.connect.ab.ca
Lines: 35
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

1. What is it?
        XDbug is a memory leak debugger.
        with a couple extras.


2. How to use it?
        link it 'libxdbug.a' with your program and include it's
        header 'xdbug.h', call 'xdbug_init(...)' with NULL to have
        all output from the library goto a file called 'xdbug.txt'
        or pass a file name for it to go.
        Now as long as DEBUG isn't defined, (before xdbug.h is included)
        then nothing different will happen, but when it is defined
        every memory allocation that your source makes
        is logged to the output file.
        The information that the output file containes
        will tell you if you have a memory leak,
        and which line and function the memory was alloced on.
        Keep in mind 'xdbug_exit()' must be called before the
        program exits or the information from malloc() and fiends
        will not be in the output file.

        The extras I mentioned earlier consist of 2 functions:
        debug() which is a printf() like function, and assert()
        which is like every other assert, but these two functions
        also output to the output file.


1.1 differs quite a bit from 1.0 so if you have already got 1.0
please get 1.1.

-- 
Top 10 reasons to procrastinate:
 1.

	Tom Fjellstrom