FreeTDS Development Group

[Andre Costa <brblueser AT uol.com.br>]

Hi Brian,

if you're on Linux, you might want to take a chance with Valgrind
[http://developer.kde.org/~sewardj/]. It appeared recently on Slashdot
when it reached the 1.0.0 milestone, and if it lives up to its claims,
it's a hell of a tool. I haven't tested it myself (not much C programming
these days, unfortunately =T ), but I've already had reports from some
people I know that it really rocks (it found some bugs that had been
hidden for a long time already).

Quoting the home page:

"Valgrind is a GPL'd tool to help you find memory-management problems in
your programs. When a program is run under Valgrind's supervision, all
reads and writes of memory are checked, and calls to
malloc/new/free/delete are intercepted. As a result, Valgrind can detect
problems such as:

* Use of uninitialised memory 
* Reading/writing memory after it has been free'd 
* Reading/writing off the end of malloc'd blocks 
* Reading/writing inappropriate areas on the stack 
* Memory leaks -- where pointers to malloc'd blocks are lost forever
* Passing of uninitialised and/or unaddressible memory to system calls
* Mismatched use of malloc/new/new [] vs free/delete/delete []
* Some misuses of the POSIX pthreads API"

HTH

Andre

On Tue, 6 Aug 2002 23:26:12 -0400 (EDT)
Brian Bruns wrote:

> Ok, I'll explain my methodology for testing memleaks in FreeTDS,
> hopefully you'll do the same such that we can figure out where the
> disconnect is.
[snip]