diff --git a/etc/vld/AUTHORS.txt b/etc/vld/AUTHORS.txt new file mode 100644 index 0000000..b70e762 --- /dev/null +++ b/etc/vld/AUTHORS.txt @@ -0,0 +1,13 @@ +------------------------------------------------ +KindDragon http://www.codeplex.com/site/users/view/KindDragon +chrisJohnson http://www.codeplex.com/site/users/view/chrisJohnson + +Contributors: (listed alphabetically) +------------------------------------------------ +benpmorgan, geordi, jerker_back, Laurent Lessieux (llessieux), snakefoot, VictorKharkov, xpol + +Many thanks to everyone who supported development without having +svn write access. + +Based on the original version (C) 2005-2009 by Dan Moulding (e-mail dmoulding@gmail.com) +http://sites.google.com/site/dmoulding/vld diff --git a/etc/vld/CHANGES.txt b/etc/vld/CHANGES.txt new file mode 100644 index 0000000..f280f41 --- /dev/null +++ b/etc/vld/CHANGES.txt @@ -0,0 +1,526 @@ +Visual Leak Detector (VLD) Version 2.4.0 + + + Change Log / Release Notes + +2.4RC (23 March 2014) +---------------------------- + Enhancements: + + VS2013 support added. + + Improved usage in C code. + + Setup rewrited to InnoSetup, autopatching common props implemented for VS2008-2013. + + Called allocation function added to printed callstack. + ! Memory leaks count fixed for case static/dynamic linked MFC. + ! Release static linked CRT detection improved (VLD_OPT_RELEASE_CRT_RUNTIME define removed). + + Bugs Fixed: + + Memory leaks with static linked CRT fixed for VS2012/2013. + + Deadlock fixed and missed memory leaks when dll loading (first appear in version 2.2.2). + +2.3 (29 April 2013) +---------------------------- + Enhancements: + + Windows 8 support added. + + Bugs Fixed: + + Memory leaks with duplicate thread id fixed (thanks to jlddodger). + +2.2.3 (15 Febrary 2012) +---------------------------- + Enhancements: + + New option VLD_OPT_RELEASE_CRT_RUNTIME added. Useful only with define VLD_FORCE_ENABLE. + + Bugs Fixed: + + Memory leaks with static linking fixed finally. + +2.2.2 (18 December 2011) +---------------------------- + Bugs Fixed: + + Memory leaks with static linking fixed. + + Visual Studio C++ 2008/2010 Express Edition compilation fixed. + + Hang fixed with GetOpenFileName(). + +2.2.1 (22 November 2011) +---------------------------- + Enhancements: + + strdup and _wcsdup functions support added. + + Preliminary support for VS 11 added. + + Bugs Fixed: + + Low performance after upgrading from VLD v2.1. + + Runtime error R6002 fixed because of wrong memory dump format. + + version.h fixed in installer. + + Some PVS studio warning fixed. + +2.2 (21 Jule 2011) +---------------------------- + Enhancements: + + New functions added: VLDSetReportHook. + + Bugs Fixed: + + Resolved call stack printing fixed. + +2.2b (8 Jule 2011) +---------------------------- + Enhancements: + + New functions added: VLDGetLeaksCount, VLDMarkAllLeaksAsReported (see vld.h). + + Introduced define called VLD_FORCE_ENABLE that allows one to active VLD even if not running in DEBUG. + + Adding Heap Validation. + + _aligned... functions and _recalloc support added. + + Memory leaks additional statistic added. + + Bugs Fixed: + + Issue fixed with loading wrong version of dbghelp.dll on Windows XP and bellow. + + VLDReportLeaks with aggregate duplicate links fixed. + + CoTaskMemAlloc memory leak detection fixed. + + Rare crash at exit on some platforms fixed. + + Asserts in release build disabled. + + LoaderLock fixed. + + LoadLibrary crash fixed with some applications like regsrv32. + + Callstack hash fixed with ASLR. + + VLDGlobalEnable fixed with new threads. + + Option VLD_OPT_MODULE_LIST_INCLUDE fixed. + +2.1 (26 March 2011) +---------------------------- + Enhancements: + + New functions added: VLDGlobalDisable, VLDGlobalEnable, VLDGetOptions, + VLDGetReportFilename, VLDSetOptions, VLDSetModulesList, + VLDGetModulesList, VLDResolveCallstacks (see vld.h). + + Option VLD_OPT_SKIP_HEAPFREE_LEAKS added. + + Hash for each leak added + + Supported loading symbols from Visual Studio symbol cache directory + + Bugs Fixed: + + Improved LdrLoadDll, GetProcAddress hooking on Windows 7. + + "HMODULE not founded" bug fixed. + + Bugs fixed when VLD off. + + Problem fixed with GetModuleHandleW for SxS dll's (mfc*.dll, msvcr*.dll). + + Unicode-to-multibyte conversion fixed. + +2.1 (26 March 2011) +---------------------------- + Enhancements: + + New functions added: VLDGlobalDisable, VLDGlobalEnable, VLDGetOptions, + VLDGetReportFilename, VLDSetOptions, VLDSetModulesList, + VLDGetModulesList, VLDResolveCallstacks (see vld.h). + + Option VLD_OPT_SKIP_HEAPFREE_LEAKS added. + + Hash for each leak added + + Supported loading symbols from Visual Studio symbol cache directory + + Bugs Fixed: + + Improved LdrLoadDll, GetProcAddress hooking on Windows 7. + + "HMODULE not founded" bug fixed. + + Bugs fixed when VLD off. + + Problem fixed with GetModuleHandleW for SxS dll's (mfc*.dll, msvcr*.dll). + + Unicode-to-multibyte conversion fixed. + +2.0b (24 August 2010) +---------------------------- + Enhancements: + + Added new commands: VLDReportLeaks, VLDRefreshModules, VLDEnableModule, + VLDDisableModule, VLDSetReportOptions (see vld.h). + + Bugs Fixed: + + Problems with MSVC 2008 SP1 fixed. Thanks to Laurent Lessieux for contributing this patch. + +2.0a (13 May 2010) +---------------------------- + Enhancements: + + Renamed vld dll files. + + Bugs Fixed: + + Problem with MSVC 2010 Unicode library fixed. + +2.0 (25 April 2010) +---------------------------- + Enhancements: + + Added support to work with 64-bit applications + + Added support to work with Visual Studio 2010 + +1.9h beta (24 February 2009) +---------------------------- + Enhancements: + + Added support to work with Visual Studio 2008. + + Known Bugs/Restrictions: + + Same bugs/restrictions as version 1.9f. + + +1.9g beta (16 April 2008) +---------------------------- + Bugs Fixed: + + Another deadlock condition may occur when loading DLLs into the process + being debugged. Special thanks to Eric Bissonnette and Kristian Paradis for + contributing this patch. + + Known Bugs/Restrictions: + + Same bugs/restrictions as version 1.9f. + + +1.9f beta (18 November 2006) +---------------------------- + Bugs Fixed: + + Deadlocks or access violations may occur when loading DLLs into + multithreaded processes. + + + In multithreaded programs, if the main thread terminates before other + threads in the process, then Visual Leak Detector may cause an access + violation while generating the memory leak report. + + Known Bugs/Restrictions: + + Memory allocations made through calls to functions loaded from a DLL using + delayed loading may not be detected. + + + Support for programs that use MFC 7.0 or MFC 7.1 is not complete yet. Some + memory leaks from such MFC-based programs may not be detected. + + + Visual Leak Detector may report leaks internal to Visual Leak Detector + if the main thread of the process terminates while other threads are still + running. + + + If more than one copy of the same C Runtime DLL is loaded in the process at + the same time, then some leaks may go undetected (note that loading more + than one copy of the C Runtime DLL into a process at the same time is + probably a bad idea to begin with). + + +1.9e beta (16 November 2006) +---------------------------- + New Features/Enhancements: + + Added a master on/off switch configuration option to vld.ini that can be + used to completely disable Visual Leak Detector. + + Bugs Fixed: + + Numerous deadlock situations. The multithread synchronization scheme has + been completely re-written which should make deadlocks in VLD much less + likely to happen. + + + An access violation will occur in VLD if GetProcAddress is called to obtain + an export's address by ordinal, for certain libraries. + + + Problems may potentially occur when the program being debugged exits due to + the Debug Help Library having been detached from the process too early. + Symptoms might include access violation exceptions or other erratic behavior + just as the program exits and while VLD is generating the leak report. + + + The copy of vld.ini installed in VLD's installation directory overrides any + other copies of vld.ini that are created, even copies placed in the + working directory of the program being debugged. + + Known Bugs/Restrictions: + + Memory allocations made through calls to functions loaded from a DLL using + delayed loading may not be detected. + + + Support for programs that use MFC 7.0 or MFC 7.1 is not complete yet. Some + memory leaks from such MFC-based programs may not be detected. + + + If more than one copy of the same C Runtime DLL is loaded in the process at + the same time, then some leaks may go undetected (note that loading more + than one copy of the C Runtime DLL into a process at the same time is + probably a bad idea to begin with). + + +1.9d beta (12 November 2006) +---------------------------- + Bugs Fixed: + + Failed assertion "freed == TRUE" pops up when running a program with VLD + without the debugger attached. + + + Some, but not all, multithreaded programs that dynamically load and unload + many DLLs have been known to experience problems, such as deadlocks or + exceptions, when used with VLD. + + + Failed assertion "exportmodule != NULL" pops up when running some programs + with VLD. + + + VLD fails to show file names or function names in the memory leak report for + some programs that are linked with the dynamic CRT library. + + + Access violation exceptions are thrown, but caught by the operating system, + when running some programs with VLD. + + +1.9c beta (6 November 2006) +--------------------------- + New Features/Enhancements: + + New NSIS installer makes setting up and using VLD much easier. + + + No need to manually copy dbghelp.dll to the right location, VLD will always + find the right version. + + + MFC 8.0 is now fully supported. + + + The memory leak report is now written to the output window much faster. + Support has been added, through a new configuration option, to slow down + the report output for older versions of Visual Studio that have trouble + when it is written too quickly. + + Bugs Fixed: + + All known compatibilities with Visual Studio 2005 have been eliminated. + + + Leaks from calloc may go undetected. + + + Leaks from vector new operator may go undetected. + + + VLDDisable and VLDEnable do not work as expected; some memory leaks that + should be ignored by VLD due to a previous call to VLDDisable are still + reported. + + + Unloading and reloading a previously loaded module may cause leaks that + occur in the module after it was reloaded to go undetected. + + + If vld.h is included in a release build, then the compiler will generate + errors if the VLDEnable or VLDDisable APIs have been used. + + +1.9b beta (26 October 2006) +--------------------------- + Bugs Fixed: + + Source compiles under Visual Studio 2005 and the binaries are compatible + with applications that link with the Visual Studio 2005 C Runtime Library + (msvcr80d.dll). + + Known Restrictions in this Release: + + Memory allocations made through calls to functions loaded from a DLL using + delayed loading may not be detected. + + + Support for programs that use MFC 7.0, MFC 7.1, or MFC 8.0 is not complete + yet. Some memory leaks from such MFC-based programs may not be detected. A + workaround for this restriction is to forcefully include the MFC DLLs in + memory leak detection, by setting the "ForceIncludeModules" configuration + option to: "mfc70d.dll mfc71d.dll mfc80d.dll" and explicitly adding vld.lib + as an input file on the linker command line (can be added through project + settings by adding it to the list of library modules in the linker options). + This restriction does not apply to programs that use MFC 4.2, which is fully + supported. + + +1.9a beta (9 March 2006) +------------------------ + New Features/Enhancements: + + All new leak detection engine detects most, if not all, in-process memory + leaks, not just leaks from "new" or "malloc", including COM-based leaks. + + + Packaged as an easier-to-use DLL. There's no longer any need to carefully + decide which modules should be linked with the VLD library. Instead, you + just include the vld.h header file in at least one source file from each + module (DLL or EXE) to be included in memory leak detection. + + + Configuration is done from an INI file instead of using preprocessor macros. + This allows VLD's configuration to be changed without needing to recompile + the program. + + + Many new configuration options have been added. One of the most often + requested option that has been added is the option to save the leak report + to a file instead of, or in addition to, the debugger. + + Bugs Fixed: + + The improved design of the new leak detection engine has resolved all of the + previously known restrictions in version 1.0. + + Known Restrictions in this Release: + + Memory allocations made through calls to functions loaded from a DLL using + delayed loading may not be detected. + + + Support for programs that use MFC 7.0, MFC 7.1, or MFC 8.0 is not complete + yet. Some memory leaks from such MFC-based programs may not be detected. A + workaround for this restriction is to forcefully include the MFC DLLs in + memory leak detection, by setting the "ForceIncludeModules" configuration + option to: "mfc70d.dll mfc71d.dll mfc80d.dll" and explicitly adding vld.lib + as an input file on the linker command line (can be added through project + settings by adding it to the list of library modules in the linker options). + This restriction does not apply to programs that use MFC 4.2, which is fully + supported. + + +1.0 (5 August 2005) +------------------- + New Features/Enhancements: + + Memory leak detection can now be selectively disabled and enabled at + runtime, using provided APIs. This provides a straightforward way of + allowing VLD to selectively "ignore" certain allocations. It can also be + used to disable VLD altogether at runtime, improving application performance + without needing to recompile. + + + If there are multiple identical memory leaks (i.e. leaks that originate from + the same call stack and that leak the same size memory block) then VLD can + optionally aggregate all of the repeated leaks, showing only the first such + leaked block in detail in the memory leak report. A tally of the total + number of leaks that match that particular size and call stack accompanies + the information for that leak. + + + When VLD is initialized at program startup, the library type which was + linked-in is displayed. This can help verify that the expected VLD library + (either single-threaded static, multithreaded static, or multithreaded DLL) + is being linked with your program. + + + The Visual Leak Detector name is displayed on most messages output to the + debugger to easily differentiate VLD's output from the output produced by + the built-in memory leak detector. + + + If any of the compile-time configuration options have been changed from + their default values, then the current state of the option is displayed in + the debugger when VLD is initialized. + + + VLD's memory leak self-checking capability (checking for leaks in VLD + itself) can be verified using a new preprocessor macro that allows VLD to + perform a self-test at runtime. + + Bugs Fixed: + + If the MFC libraries are statically linked to the program being debugged, + then MFC will erroneously report memory leaks in the Visual Leak Detector + code and may cause an access violation while attempting to report the false + memory leaks. These bogus leaks are always reported as "client block at +
, subtype bf42" and are claimed to be "invalid objects". + + + VLD will leak a fixed-sized block of memory when the program exits if VLD + failed to initialize because the Debug Help library (dbghelp.dll) could not + be loaded. + + + In multithreaded programs, if the program's main thread terminates before + other threads in the same process, then VLD may cause an access violation + while freeing resources used internally by VLD. + + +0.9i beta (30 April 2005) +------------------------- + New Features/Enhancements: + + Added support in the source code for x64 architecture. The pre-built + libraries will continue to support 32-bit only. If you need 64-bit support + you'll need to build 64-bit versions of the libraries from source. Note that + x64 is the only 64-bit architecture supported at this time. Itanium (aka + IA-64) is NOT currently supported. + + Bugs Fixed: + + VLD does not report memory leaks that are the result of a failure to free + memory allocated via a call to realloc(). + + In multithreaded programs, if the program's main thread terminates before + other threads in the same process, then VLD may cause an access violation + while checking for memory leaks. + + If VLD cannot find the source file and line number information for a program + address, the last known file and line number will be repeated in the call + stack section of the memory leak report. The correct behavior should be for + VLD to print "File and line number not available" for that call stack entry. + + +0.9h beta (22 April 2005) +------------------------- + Bugs Fixed: + + Access Violations occur at random places within the VLD code when using + VLD version 0.9g. + + When using VLD version 0.9g, VLD may fail to report some memory leaks. + + +0.9g beta (22 April 2005) +------------------------- + New Features/Enhancements: + + Replaced the temporary internal search algorithm with a permanent search + algorithm that is much faster. Programs that dynamically allocate a large + number of memory blocks (tens of thousands or more) will see the most + significant performance boost from this version of VLD versus the previous + version. Overall, this is the fastest version of VLD released to date. + + +0.9f beta (13 April 2005) +------------------------- + New Features/Enhancements: + + Changed the internal search algorithm to a temporary simpler, but + more stable algorithm. A permanent algorithm which should be much + more efficient will be in a forthcoming release. + + Bugs Fixed: + + Access Violation at line 319 in vldutil.cpp may occur when running a + program linked with the VLD library. + + +0.9e beta (12 April 2005) +------------------------- + New Features/Enhancements: + + VLD no longer uses any STL containers or STL strings. This solves all of the + compatibility problems with Visual Studio .NET when using the pre-built + VLD libraries. + + + The configuration preprocessor macros now work with C programs without the + need to call VLDConfigure from within the program being debugged. + Because VLDConfigure is now obsolete, it has been removed. + + + One new source file (vldutil.cpp) and one new header (vldutil.h) have been + added. They contain utility functions and utility classes that replace + functionality previously performed by STL containers and strings. + + + The VisualLeakDetector global class object is now constructed at C runtime + initialization (i.e. it resides in the "compiler" initialization area). + Because VLD no longer uses any STL components, there is no longer the risk + that VLD will conflict with any STL libraries that also are constructed at + C runtime initialization. The end result is that VLD starts running earlier + and is destroyed later, which leads to more accurate leak detection. + + Bugs Fixed: + + Linking to the VLD 0.9d libraries from the VLD distribution under Visual + Studio .NET results in a number of linker "unresolved external symbol" + errors. Unresolved symbols include "__declspec(dllimport) void __cdecl + std::_Xran(void)" and "__declspec(dllimport) private: void __thiscall + std::basic_string,class std::allocator >::_Eos(unsigned int)", among others. + + + Call stacks do not appear in the memory leak report when linking against + release VLD libraries built from source with Visual Studio .NET. + + + If the preprocessor macro VLD_MAX_DATA_DUMP is defined as 0 (zero), then VLD + will get stuck in an infinite loop, repeatedly printing the same information + while attempting to display the memory leak report in the debugger's output + window. + + +0.9d beta (30 March 2005) +------------------------- + New Features/Enhancements: + + 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 library. 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. + + +0.9c beta (17 March 2005) +------------------------- + Bugs Fixed: + + 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. + + +0.9b beta (15 March 2005) +------------------------- + Bugs Fixed: + + 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. + + +0.9a beta (12 March 2005) +------------------------- + Initial Public Release + + + + + + + + + + + + diff --git a/etc/vld/COPYING.txt b/etc/vld/COPYING.txt new file mode 100644 index 0000000..073dd57 --- /dev/null +++ b/etc/vld/COPYING.txt @@ -0,0 +1,458 @@ + GNU LESSER GENERAL PUBLIC LICENSE + Version 2.1, February 1999 + + Copyright (C) 1991, 1999 Free Software Foundation, Inc. + 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + +[This is the first released version of the Lesser GPL. It also counts + as the successor of the GNU Library Public License, version 2, hence + the version number 2.1.] + + Preamble + + The licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +Licenses are intended to guarantee your freedom to share and change +free software--to make sure the software is free for all its users. + + This license, the Lesser General Public License, applies to some +specially designated software packages--typically libraries--of the +Free Software Foundation and other authors who decide to use it. You +can use it too, but we suggest you first think carefully about whether +this license or the ordinary General Public License is the better +strategy to use in any particular case, based on the explanations below. + + When we speak of free software, we are referring to freedom of use, +not price. Our General Public Licenses are designed to make sure that +you have the freedom to distribute copies of free software (and charge +for this service if you wish); that you receive source code or can get +it if you want it; that you can change the software and use pieces of +it in new free programs; and that you are informed that you can do +these things. + + To protect your rights, we need to make restrictions that forbid +distributors to deny you these rights or to ask you to surrender these +rights. These restrictions translate to certain responsibilities for +you if you distribute copies of the library or if you modify it. + + For example, if you distribute copies of the library, whether gratis +or for a fee, you must give the recipients all the rights that we gave +you. You must make sure that they, too, receive or can get the source +code. If you link other code with the library, you must provide +complete object files to the recipients, so that they can relink them +with the library after making changes to the library and recompiling +it. And you must show them these terms so they know their rights. + + We protect your rights with a two-step method: (1) we copyright the +library, and (2) we offer you this license, which gives you legal +permission to copy, distribute and/or modify the library. + + To protect each distributor, we want to make it very clear that +there is no warranty for the free library. Also, if the library is +modified by someone else and passed on, the recipients should know +that what they have is not the original version, so that the original +author's reputation will not be affected by problems that might be +introduced by others. + + Finally, software patents pose a constant threat to the existence of +any free program. We wish to make sure that a company cannot +effectively restrict the users of a free program by obtaining a +restrictive license from a patent holder. Therefore, we insist that +any patent license obtained for a version of the library must be +consistent with the full freedom of use specified in this license. + + Most GNU software, including some libraries, is covered by the +ordinary GNU General Public License. This license, the GNU Lesser +General Public License, applies to certain designated libraries, and +is quite different from the ordinary General Public License. We use +this license for certain libraries in order to permit linking those +libraries into non-free programs. + + When a program is linked with a library, whether statically or using +a shared library, the combination of the two is legally speaking a +combined work, a derivative of the original library. The ordinary +General Public License therefore permits such linking only if the +entire combination fits its criteria of freedom. The Lesser General +Public License permits more lax criteria for linking other code with +the library. + + We call this license the "Lesser" General Public License because it +does Less to protect the user's freedom than the ordinary General +Public License. It also provides other free software developers Less +of an advantage over competing non-free programs. These disadvantages +are the reason we use the ordinary General Public License for many +libraries. However, the Lesser license provides advantages in certain +special circumstances. + + For example, on rare occasions, there may be a special need to +encourage the widest possible use of a certain library, so that it becomes +a de-facto standard. To achieve this, non-free programs must be +allowed to use the library. A more frequent case is that a free +library does the same job as widely used non-free libraries. In this +case, there is little to gain by limiting the free library to free +software only, so we use the Lesser General Public License. + + In other cases, permission to use a particular library in non-free +programs enables a greater number of people to use a large body of +free software. For example, permission to use the GNU C Library in +non-free programs enables many more people to use the whole GNU +operating system, as well as its variant, the GNU/Linux operating +system. + + Although the Lesser General Public License is Less protective of the +users' freedom, it does ensure that the user of a program that is +linked with the Library has the freedom and the wherewithal to run +that program using a modified version of the Library. + + The precise terms and conditions for copying, distribution and +modification follow. Pay close attention to the difference between a +"work based on the library" and a "work that uses the library". The +former contains code derived from the library, whereas the latter must +be combined with the library in order to run. + + GNU LESSER GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License Agreement applies to any software library or other +program which contains a notice placed by the copyright holder or +other authorized party saying it may be distributed under the terms of +this Lesser General Public License (also called "this License"). +Each licensee is addressed as "you". + + A "library" means a collection of software functions and/or data +prepared so as to be conveniently linked with application programs +(which use some of those functions and data) to form executables. + + The "Library", below, refers to any such software library or work +which has been distributed under these terms. A "work based on the +Library" means either the Library or any derivative work under +copyright law: that is to say, a work containing the Library or a +portion of it, either verbatim or with modifications and/or translated +straightforwardly into another language. (Hereinafter, translation is +included without limitation in the term "modification".) + + "Source code" for a work means the preferred form of the work for +making modifications to it. For a library, complete source code means +all the source code for all modules it contains, plus any associated +interface definition files, plus the scripts used to control compilation +and installation of the library. + + Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running a program using the Library is not restricted, and output from +such a program is covered only if its contents constitute a work based +on the Library (independent of the use of the Library in a tool for +writing it). Whether that is true depends on what the Library does +and what the program that uses the Library does. + + 1. You may copy and distribute verbatim copies of the Library's +complete source code as you receive it, in any medium, provided that +you conspicuously and appropriately publish on each copy an +appropriate copyright notice and disclaimer of warranty; keep intact +all the notices that refer to this License and to the absence of any +warranty; and distribute a copy of this License along with the +Library. + + You may charge a fee for the physical act of transferring a copy, +and you may at your option offer warranty protection in exchange for a +fee. + + 2. You may modify your copy or copies of the Library or any portion +of it, thus forming a work based on the Library, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + + a) The modified work must itself be a software library. + + b) You must cause the files modified to carry prominent notices + stating that you changed the files and the date of any change. + + c) You must cause the whole of the work to be licensed at no + charge to all third parties under the terms of this License. + + d) If a facility in the modified Library refers to a function or a + table of data to be supplied by an application program that uses + the facility, other than as an argument passed when the facility + is invoked, then you must make a good faith effort to ensure that, + in the event an application does not supply such function or + table, the facility still operates, and performs whatever part of + its purpose remains meaningful. + + (For example, a function in a library to compute square roots has + a purpose that is entirely well-defined independent of the + application. Therefore, Subsection 2d requires that any + application-supplied function or table used by this function must + be optional: if the application does not supply it, the square + root function must still compute square roots.) + +These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Library, +and can be reasonably considered independent and separate works in +themselves, then this License, and its terms, do not apply to those +sections when you distribute them as separate works. But when you +distribute the same sections as part of a whole which is a work based +on the Library, the distribution of the whole must be on the terms of +this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote +it. + +Thus, it is not the intent of this section to claim rights or contest +your rights to work written entirely by you; rather, the intent is to +exercise the right to control the distribution of derivative or +collective works based on the Library. + +In addition, mere aggregation of another work not based on the Library +with the Library (or with a work based on the Library) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. + + 3. You may opt to apply the terms of the ordinary GNU General Public +License instead of this License to a given copy of the Library. To do +this, you must alter all the notices that refer to this License, so +that they refer to the ordinary GNU General Public License, version 2, +instead of to this License. (If a newer version than version 2 of the +ordinary GNU General Public License has appeared, then you can specify +that version instead if you wish.) Do not make any other change in +these notices. + + Once this change is made in a given copy, it is irreversible for +that copy, so the ordinary GNU General Public License applies to all +subsequent copies and derivative works made from that copy. + + This option is useful when you wish to copy part of the code of +the Library into a program that is not a library. + + 4. You may copy and distribute the Library (or a portion or +derivative of it, under Section 2) in object code or executable form +under the terms of Sections 1 and 2 above provided that you accompany +it with the complete corresponding machine-readable source code, which +must be distributed under the terms of Sections 1 and 2 above on a +medium customarily used for software interchange. + + If distribution of object code is made by offering access to copy +from a designated place, then offering equivalent access to copy the +source code from the same place satisfies the requirement to +distribute the source code, even though third parties are not +compelled to copy the source along with the object code. + + 5. A program that contains no derivative of any portion of the +Library, but is designed to work with the Library by being compiled or +linked with it, is called a "work that uses the Library". Such a +work, in isolation, is not a derivative work of the Library, and +therefore falls outside the scope of this License. + + However, linking a "work that uses the Library" with the Library +creates an executable that is a derivative of the Library (because it +contains portions of the Library), rather than a "work that uses the +library". The executable is therefore covered by this License. +Section 6 states terms for distribution of such executables. + + When a "work that uses the Library" uses material from a header file +that is part of the Library, the object code for the work may be a +derivative work of the Library even though the source code is not. +Whether this is true is especially significant if the work can be +linked without the Library, or if the work is itself a library. The +threshold for this to be true is not precisely defined by law. + + If such an object file uses only numerical parameters, data +structure layouts and accessors, and small macros and small inline +functions (ten lines or less in length), then the use of the object +file is unrestricted, regardless of whether it is legally a derivative +work. (Executables containing this object code plus portions of the +Library will still fall under Section 6.) + + Otherwise, if the work is a derivative of the Library, you may +distribute the object code for the work under the terms of Section 6. +Any executables containing that work also fall under Section 6, +whether or not they are linked directly with the Library itself. + + 6. As an exception to the Sections above, you may also combine or +link a "work that uses the Library" with the Library to produce a +work containing portions of the Library, and distribute that work +under terms of your choice, provided that the terms permit +modification of the work for the customer's own use and reverse +engineering for debugging such modifications. + + You must give prominent notice with each copy of the work that the +Library is used in it and that the Library and its use are covered by +this License. You must supply a copy of this License. If the work +during execution displays copyright notices, you must include the +copyright notice for the Library among them, as well as a reference +directing the user to the copy of this License. Also, you must do one +of these things: + + a) Accompany the work with the complete corresponding + machine-readable source code for the Library including whatever + changes were used in the work (which must be distributed under + Sections 1 and 2 above); and, if the work is an executable linked + with the Library, with the complete machine-readable "work that + uses the Library", as object code and/or source code, so that the + user can modify the Library and then relink to produce a modified + executable containing the modified Library. (It is understood + that the user who changes the contents of definitions files in the + Library will not necessarily be able to recompile the application + to use the modified definitions.) + + b) Use a suitable shared library mechanism for linking with the + Library. A suitable mechanism is one that (1) uses at run time a + copy of the library already present on the user's computer system, + rather than copying library functions into the executable, and (2) + will operate properly with a modified version of the library, if + the user installs one, as long as the modified version is + interface-compatible with the version that the work was made with. + + c) Accompany the work with a written offer, valid for at + least three years, to give the same user the materials + specified in Subsection 6a, above, for a charge no more + than the cost of performing this distribution. + + d) If distribution of the work is made by offering access to copy + from a designated place, offer equivalent access to copy the above + specified materials from the same place. + + e) Verify that the user has already received a copy of these + materials or that you have already sent this user a copy. + + For an executable, the required form of the "work that uses the +Library" must include any data and utility programs needed for +reproducing the executable from it. However, as a special exception, +the materials to be distributed need not include anything that is +normally distributed (in either source or binary form) with the major +components (compiler, kernel, and so on) of the operating system on +which the executable runs, unless that component itself accompanies +the executable. + + It may happen that this requirement contradicts the license +restrictions of other proprietary libraries that do not normally +accompany the operating system. Such a contradiction means you cannot +use both them and the Library together in an executable that you +distribute. + + 7. You may place library facilities that are a work based on the +Library side-by-side in a single library together with other library +facilities not covered by this License, and distribute such a combined +library, provided that the separate distribution of the work based on +the Library and of the other library facilities is otherwise +permitted, and provided that you do these two things: + + a) Accompany the combined library with a copy of the same work + based on the Library, uncombined with any other library + facilities. This must be distributed under the terms of the + Sections above. + + b) Give prominent notice with the combined library of the fact + that part of it is a work based on the Library, and explaining + where to find the accompanying uncombined form of the same work. + + 8. You may not copy, modify, sublicense, link with, or distribute +the Library except as expressly provided under this License. Any +attempt otherwise to copy, modify, sublicense, link with, or +distribute the Library is void, and will automatically terminate your +rights under this License. However, parties who have received copies, +or rights, from you under this License will not have their licenses +terminated so long as such parties remain in full compliance. + + 9. You are not required to accept this License, since you have not +signed it. However, nothing else grants you permission to modify or +distribute the Library or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Library (or any work based on the +Library), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Library or works based on it. + + 10. Each time you redistribute the Library (or any work based on the +Library), the recipient automatically receives a license from the +original licensor to copy, distribute, link with or modify the Library +subject to these terms and conditions. You may not impose any further +restrictions on the recipients' exercise of the rights granted herein. +You are not responsible for enforcing compliance by third parties with +this License. + + 11. If, as a consequence of a court judgment or allegation of patent +infringement or for any other reason (not limited to patent issues), +conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot +distribute so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you +may not distribute the Library at all. For example, if a patent +license would not permit royalty-free redistribution of the Library by +all those who receive copies directly or indirectly through you, then +the only way you could satisfy both it and this License would be to +refrain entirely from distribution of the Library. + +If any portion of this section is held invalid or unenforceable under any +particular circumstance, the balance of the section is intended to apply, +and the section as a whole is intended to apply in other circumstances. + +It is not the purpose of this section to induce you to infringe any +patents or other property right claims or to contest validity of any +such claims; this section has the sole purpose of protecting the +integrity of the free software distribution system which is +implemented by public license practices. Many people have made +generous contributions to the wide range of software distributed +through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is willing +to distribute software through any other system and a licensee cannot +impose that choice. + +This section is intended to make thoroughly clear what is believed to +be a consequence of the rest of this License. + + 12. If the distribution and/or use of the Library is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Library under this License may add +an explicit geographical distribution limitation excluding those countries, +so that distribution is permitted only in or among countries not thus +excluded. In such case, this License incorporates the limitation as if +written in the body of this License. + + 13. The Free Software Foundation may publish revised and/or new +versions of the Lesser General Public License from time to time. +Such new versions will be similar in spirit to the present version, +but may differ in detail to address new problems or concerns. + +Each version is given a distinguishing version number. If the Library +specifies a version number of this License which applies to it and +"any later version", you have the option of following the terms and +conditions either of that version or of any later version published by +the Free Software Foundation. If the Library does not specify a +license version number, you may choose any version ever published by +the Free Software Foundation. + + 14. If you wish to incorporate parts of the Library into other free +programs whose distribution conditions are incompatible with these, +write to the author to ask for permission. For software which is +copyrighted by the Free Software Foundation, write to the Free +Software Foundation; we sometimes make exceptions for this. Our +decision will be guided by the two goals of preserving the free status +of all derivatives of our free software and of promoting the sharing +and reuse of software generally. + + NO WARRANTY + + 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO +WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. +EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR +OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY +KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE +IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE +LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME +THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. + + 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN +WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY +AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU +FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR +CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE +LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING +RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A +FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF +SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH +DAMAGES. + + END OF TERMS AND CONDITIONS \ No newline at end of file diff --git a/etc/vld/bin/Win32/vld_x86.dll b/etc/vld/bin/Win32/vld_x86.dll deleted file mode 100644 index 5361833..0000000 Binary files a/etc/vld/bin/Win32/vld_x86.dll and /dev/null differ diff --git a/etc/vld/include/vld.h b/etc/vld/include/vld.h index 29d1216..52686dc 100644 --- a/etc/vld/include/vld.h +++ b/etc/vld/include/vld.h @@ -1,7 +1,7 @@ //////////////////////////////////////////////////////////////////////////////// // // Visual Leak Detector - Import Library Header -// Copyright (c) 2005-2012 VLD Team +// Copyright (c) 2005-2014 VLD Team // // This library is free software; you can redistribute it and/or // modify it under the terms of the GNU Lesser General Public @@ -25,9 +25,12 @@ #include "vld_def.h" -#if defined _DEBUG || defined VLD_FORCE_ENABLE +typedef int VLD_BOOL; +typedef unsigned int VLD_UINT; +typedef size_t VLD_SIZET; +typedef void* VLD_HMODULE; -#include +#if defined _DEBUG || defined VLD_FORCE_ENABLE #pragma comment(lib, "vld.lib") @@ -123,7 +126,17 @@ __declspec(dllimport) void VLDGlobalEnable (); // // None. // -__declspec(dllimport) UINT VLDReportLeaks (); +__declspec(dllimport) VLD_UINT VLDReportLeaks (); + +// VLDReportThreadLeaks - Report thread leaks up to the execution point. +// +// threadId: thread Id. +// +// Return Value: +// +// None. +// +__declspec(dllimport) VLD_UINT VLDReportThreadLeaks (VLD_UINT threadId); // VLDGetLeaksCount - Return memory leaks count to the execution point. // @@ -131,7 +144,17 @@ __declspec(dllimport) UINT VLDReportLeaks (); // // None. // -__declspec(dllimport) UINT VLDGetLeaksCount (); +__declspec(dllimport) VLD_UINT VLDGetLeaksCount (); + +// VLDGetThreadLeaksCount - Return thread memory leaks count to the execution point. +// +// threadId: thread Id. +// +// Return Value: +// +// None. +// +__declspec(dllimport) VLD_UINT VLDGetThreadLeaksCount (VLD_UINT threadId); // VLDMarkAllLeaksAsReported - Mark all leaks as reported. // @@ -141,6 +164,16 @@ __declspec(dllimport) UINT VLDGetLeaksCount (); // __declspec(dllimport) void VLDMarkAllLeaksAsReported (); +// VLDMarkThreadLeaksAsReported - Mark thread leaks as reported. +// +// threadId: thread Id. +// +// Return Value: +// +// None. +// +__declspec(dllimport) void VLDMarkThreadLeaksAsReported (VLD_UINT threadId); + // VLDRefreshModules - Look for recently loaded DLLs and patch them if necessary. // @@ -160,7 +193,7 @@ __declspec(dllimport) void VLDRefreshModules(); // None. // -__declspec(dllimport) void VLDEnableModule(HMODULE module); +__declspec(dllimport) void VLDEnableModule(VLD_HMODULE module); // VLDDisableModule - Disable Memory leak checking on the specified module. @@ -171,7 +204,7 @@ __declspec(dllimport) void VLDEnableModule(HMODULE module); // // None. // -__declspec(dllimport) void VLDDisableModule(HMODULE module); +__declspec(dllimport) void VLDDisableModule(VLD_HMODULE module); // VLDGetOptions - Return all current options. // @@ -179,7 +212,7 @@ __declspec(dllimport) void VLDDisableModule(HMODULE module); // // Mask of current options. // -__declspec(dllimport) UINT VLDGetOptions(); +__declspec(dllimport) VLD_UINT VLDGetOptions(); // VLDGetReportFilename - Return current report filename. // @@ -189,7 +222,7 @@ __declspec(dllimport) UINT VLDGetOptions(); // // None. // -__declspec(dllimport) void VLDGetReportFilename(WCHAR *filename); +__declspec(dllimport) void VLDGetReportFilename(wchar_t *filename); // VLDSetOptions - Update the report options via function call rather than INI file. // @@ -211,7 +244,7 @@ __declspec(dllimport) void VLDGetReportFilename(WCHAR *filename); // // None. // -__declspec(dllimport) void VLDSetOptions(UINT option_mask, SIZE_T maxDataDump, UINT maxTraceFrames); +__declspec(dllimport) void VLDSetOptions(VLD_UINT option_mask, VLD_SIZET maxDataDump, VLD_UINT maxTraceFrames); // VLDSetModulesList - Set list of modules included/excluded in leak detection // depending on parameter "includeModules". @@ -224,7 +257,7 @@ __declspec(dllimport) void VLDSetOptions(UINT option_mask, SIZE_T maxDataDump, U // // None. // -__declspec(dllimport) void VLDSetModulesList(CONST WCHAR *modules, BOOL includeModules); +__declspec(dllimport) void VLDSetModulesList(const wchar_t *modules, VLD_BOOL includeModules); // VLDGetModulesList - Return current list of included/excluded modules // depending on flag VLD_OPT_TRACE_INTERNAL_FRAMES. @@ -235,9 +268,9 @@ __declspec(dllimport) void VLDSetModulesList(CONST WCHAR *modules, BOOL includeM // // Return Value: // -// BOOL: TRUE if include modules, otherwise FALSE. +// VLD_BOOL: TRUE if include modules, otherwise FALSE. // -__declspec(dllimport) BOOL VLDGetModulesList(WCHAR *modules, UINT size); +__declspec(dllimport) VLD_BOOL VLDGetModulesList(wchar_t *modules, VLD_UINT size); // VLDSetReportOptions - Update the report options via function call rather than INI file. // @@ -253,7 +286,7 @@ __declspec(dllimport) BOOL VLDGetModulesList(WCHAR *modules, UINT size); // // None. // -__declspec(dllimport) void VLDSetReportOptions(UINT option_mask, CONST WCHAR *filename); +__declspec(dllimport) void VLDSetReportOptions(VLD_UINT option_mask, const wchar_t *filename); // VLDSetReportHook - Installs or uninstalls a client-defined reporting function by hooking it // into the C run-time debug reporting process (debug version only). @@ -290,18 +323,21 @@ __declspec(dllexport) void VLDResolveCallstacks(); #define VLDEnable() #define VLDDisable() #define VLDRestore() -#define VLDReportLeaks() 0 -#define VLDGetLeaksCount() 0 +#define VLDReportLeaks() (0) +#define VLDReportThreadLeaks() (0) +#define VLDGetLeaksCount() (0) +#define VLDGetThreadLeaksCount() (0) #define VLDMarkAllLeaksAsReported() +#define VLDMarkThreadLeaksAsReported(a) #define VLDRefreshModules() #define VLDEnableModule(a) #define VLDDisableModule(b) -#define VLDGetOptions() 0 +#define VLDGetOptions() (0) #define VLDGetReportFilename(a) #define VLDSetOptions(a, b, c) #define VLDSetReportHook(a, b) #define VLDSetModulesList(a) -#define VLDGetModulesList(a, b) FALSE +#define VLDGetModulesList(a, b) (FALSE) #define VLDSetReportOptions(a, b) #endif // _DEBUG diff --git a/etc/vld/include/vld_def.h b/etc/vld/include/vld_def.h index 252835d..4b6d92e 100644 --- a/etc/vld/include/vld_def.h +++ b/etc/vld/include/vld_def.h @@ -1,7 +1,7 @@ //////////////////////////////////////////////////////////////////////////////// // // Visual Leak Detector - Import Library Header -// Copyright (c) 2005-2012 VLD Team +// Copyright (c) 2005-2014 VLD Team // // This library is free software; you can redistribute it and/or // modify it under the terms of the GNU Lesser General Public @@ -23,6 +23,8 @@ #pragma once +#include + #define VLD_OPT_AGGREGATE_DUPLICATES 0x0001 // If set, aggregate duplicate leaks in the leak report. #define VLD_OPT_MODULE_LIST_INCLUDE 0x0002 // If set, modules in the module list are included, all others are excluded. #define VLD_OPT_REPORT_TO_DEBUGGER 0x0004 // If set, the memory leak report is sent to the debugger. @@ -37,7 +39,6 @@ #define VLD_OPT_REPORT_TO_STDOUT 0x0800 // If set, the memory leak report is sent to stdout. #define VLD_OPT_SKIP_HEAPFREE_LEAKS 0x1000 // If set, VLD skip HeapFree memory leaks. #define VLD_OPT_VALIDATE_HEAPFREE 0x2000 // If set, VLD verifies and reports heap consistency for HeapFree calls. -#define VLD_OPT_RELEASE_CRT_RUNTIME 0x4000 // If set, VLD treat CRT runtime as release version (use only with define VLD_FORCE_ENABLE). #define VLD_RPTHOOK_INSTALL 0 #define VLD_RPTHOOK_REMOVE 1 diff --git a/etc/vld/bin/Win32/Microsoft.DTfW.DHL.manifest b/etc/vld/lib/Win32/Debug/Microsoft.DTfW.DHL.manifest similarity index 100% rename from etc/vld/bin/Win32/Microsoft.DTfW.DHL.manifest rename to etc/vld/lib/Win32/Debug/Microsoft.DTfW.DHL.manifest diff --git a/etc/vld/bin/Win32/dbghelp.dll b/etc/vld/lib/Win32/Debug/dbghelp.dll similarity index 100% rename from etc/vld/bin/Win32/dbghelp.dll rename to etc/vld/lib/Win32/Debug/dbghelp.dll diff --git a/etc/vld/lib/Win32/Debug/vld.ini b/etc/vld/lib/Win32/Debug/vld.ini new file mode 100644 index 0000000..bd8ef6b --- /dev/null +++ b/etc/vld/lib/Win32/Debug/vld.ini @@ -0,0 +1,34 @@ +;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; +;; +;; Visual Leak Detector - Initialization/Configuration File +;; Copyright (c) 2006 Dan Moulding +;; +;; This library is free software; you can redistribute it and/or +;; modify it under the terms of the GNU Lesser General Public +;; License as published by the Free Software Foundation; either +;; version 2.1 of the License, or (at your option) any later version. +;; +;; This library is distributed in the hope that it will be useful, +;; but WITHOUT ANY WARRANTY; without even the implied warranty of +;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU +;; Lesser General Public License for more details. +;; +;; You should have received a copy of the GNU Lesser General Public +;; License along with this library; if not, write to the Free Software +;; Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA +;; +;; See COPYING.txt for the full terms of the GNU Lesser General Public License. +;; +;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; + +; Any options left blank or not present will revert to their default values. +[Options] + +; The main on/off switch. If off, Visual Leak Detector will be completely +; disabled. It will do nothing but print a message to the debugger indicating +; that it has been turned off. +; +; Valid Values: on, off +; Default: on +; +VLD = on diff --git a/etc/vld/lib/Win32/Debug/vld_x86.dll b/etc/vld/lib/Win32/Debug/vld_x86.dll new file mode 100644 index 0000000..526c82e Binary files /dev/null and b/etc/vld/lib/Win32/Debug/vld_x86.dll differ diff --git a/etc/vld/lib/Win32/vld.lib b/etc/vld/lib/Win32/vld.lib index 08fc4c1..a95e278 100644 Binary files a/etc/vld/lib/Win32/vld.lib and b/etc/vld/lib/Win32/vld.lib differ diff --git a/etc/vld/lib/Win64/Debug/Microsoft.DTfW.DHL.manifest b/etc/vld/lib/Win64/Debug/Microsoft.DTfW.DHL.manifest new file mode 100644 index 0000000..1ea64d5 --- /dev/null +++ b/etc/vld/lib/Win64/Debug/Microsoft.DTfW.DHL.manifest @@ -0,0 +1,7 @@ + + + + + + + diff --git a/etc/vld/lib/Win64/Debug/dbghelp.dll b/etc/vld/lib/Win64/Debug/dbghelp.dll new file mode 100644 index 0000000..499fa29 Binary files /dev/null and b/etc/vld/lib/Win64/Debug/dbghelp.dll differ diff --git a/etc/vld/lib/Win64/Debug/vld.ini b/etc/vld/lib/Win64/Debug/vld.ini new file mode 100644 index 0000000..bd8ef6b --- /dev/null +++ b/etc/vld/lib/Win64/Debug/vld.ini @@ -0,0 +1,34 @@ +;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; +;; +;; Visual Leak Detector - Initialization/Configuration File +;; Copyright (c) 2006 Dan Moulding +;; +;; This library is free software; you can redistribute it and/or +;; modify it under the terms of the GNU Lesser General Public +;; License as published by the Free Software Foundation; either +;; version 2.1 of the License, or (at your option) any later version. +;; +;; This library is distributed in the hope that it will be useful, +;; but WITHOUT ANY WARRANTY; without even the implied warranty of +;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU +;; Lesser General Public License for more details. +;; +;; You should have received a copy of the GNU Lesser General Public +;; License along with this library; if not, write to the Free Software +;; Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA +;; +;; See COPYING.txt for the full terms of the GNU Lesser General Public License. +;; +;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; + +; Any options left blank or not present will revert to their default values. +[Options] + +; The main on/off switch. If off, Visual Leak Detector will be completely +; disabled. It will do nothing but print a message to the debugger indicating +; that it has been turned off. +; +; Valid Values: on, off +; Default: on +; +VLD = on diff --git a/etc/vld/lib/Win64/Debug/vld_x64.dll b/etc/vld/lib/Win64/Debug/vld_x64.dll new file mode 100644 index 0000000..06682c1 Binary files /dev/null and b/etc/vld/lib/Win64/Debug/vld_x64.dll differ diff --git a/etc/vld/lib/Win64/vld.lib b/etc/vld/lib/Win64/vld.lib index 7ca0a44..6325a37 100644 Binary files a/etc/vld/lib/Win64/vld.lib and b/etc/vld/lib/Win64/vld.lib differ