|
Visual Leak Detector (VLD) Version 0.9d
Change Log / Release Notes
New Features/Changes:
---------------------
Changes in Version 0.9d (30 March 2005)
---------------------------------------
+ This version of VLD brings with it some major changes to the way VLD
interfaces with programs that use it. Instead of requiring that VLD be built
from source and then linked with the application, VLD is now packaged as a
pre-built static libaray. For those who just want to use VLD and are not
interested in modifying the source, this eliminates the complexities of
building VLD from source. A single header file, vld.h, has been added. To
link with the static library, this header needs to be included in one of the
program's source files. Please see the README.txt file for details on how
these changes affect how to use Visual Leak Detector.
+ The Microsoft Debug Help Library (dbghelp.dll) version 6.3 is now included
with the VLD distribution.
Bug Fixes:
----------
Problems Fixed in Verson 0.9c (17 March 2005)
---------------------------------------------
+ Compile error, "error C2039: 'size' : is not a member of '_CrtMemBlockHeader'"
occurs at line 644 of vld.cpp when building VLD with the VLD_MAX_DATA_DUMP
preprocessor macro defined.
Problems Fixed in Version 0.9b (15 March 2005)
----------------------------------------------
+ VLD fails to detect memory leaks in class constructors if the objects
constructed are global objects.
+ If a debug executable is built with certain compiler optimizations turned on,
specifically frame pointer omission optimization or automatic inlining, then
theoretically VLD may produce incomplete or inaccurate stack traces or might
fail to produce stack traces altogether.
|
By viewing downloads associated with this article you agree to the Terms of Service and the article's licence.
If a file you wish to view isn't highlighted, and is a text file (not binary), please
let us know and we'll add colourisation support for it.
This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.
A list of licenses authors might use can be found here
In real life I'm a firmware engineer. I mostly do C and assembly programming on obscure proprietary hardware. But I started my programming career doing a lot of C++. So, occassionally in my free time I enjoy dabbling in my own Windows programming projects with Visual C++ to keep my C++ skills from rotting away completely.
I also like to keep abreast of the GNU/Linux scene because, well let's face it, Windows isn't everything. I've recently found Cygwin to be a good way of getting the best of both worlds.