Open Hub
Black Duck Open Hub

 Settings |  Report Duplicate

1
I Use This!
Very Low Activity

Commits : Listings

Analyzed 3 days ago. based on code collected 3 days ago.
May 31, 2023 — May 31, 2024
Commit Message Contributor Files Modified Lines Added Lines Removed Code Location Date
Updated for the 1.9f release.d
dmouldin
More... over 17 years ago
Bumped version to 1.9f.
dmouldin
More... over 17 years ago
Updated for the 1.9f release.
dmouldin
More... over 17 years ago
Added code to the destructor to have VLD wait for still-running threads to terminate. This ensures that the leak report is generated in a single-threaded environment, and also gives VLD a chance to warn the user that the leak report may not be totally accurate because threads may not be terminating gracefully.
dmouldin
More... over 17 years ago
Removed version numbers from the comments heading of every source file. Updating the version in every file for each patch and release is just going to unnecessarily bloat the file histories.
dmouldin
More... over 17 years ago
Narrowed the scope of the loader lock so that it just protects the call to EnumerateLoadedModules64. Having too broad a scope was probably the cause of some deadlocks. Also, fixed uprotected access to the loaded modules ModuleSet in attachtoloadedmodules that could have been causing some access violations due to an invalidated Iterator.
dmouldin
More... over 17 years ago
Changed the installation of the private assemblies, so that they are installed directly into the bin directory instead of in their own named directories. Bumped the version to 1.9e.
dmouldin
More... over 17 years ago
Fixed XHTML compliance error related to the blockquote.
dmouldin
More... over 17 years ago
Fixed option initialization bug, where the option values read from vld.ini get wiped out because they are read first and then initialized. Also fixed GetProcAddress so it won't crash if a request is made for an MFC export by ordinal.
dmouldin
More... over 17 years ago
Added documentation for the master on/off switch configuration option.
dmouldin
More... over 17 years ago
Added the master on/off switch configuration option. Also added a fixed bug (GetProcAddress may crash if an export is requested by ordinal for MFC modules).
dmouldin
More... over 17 years ago
Added the master on/off switch configuration option. If off, then VLD is completely disabled.
dmouldin
More... over 17 years ago
Added checks for the state of the master on/off switch configuration option. If off, then the APIs do nothing.
dmouldin
More... over 17 years ago
Added the master on/off switch configuration option, to optionally completely disable VLD.
dmouldin
More... over 17 years ago
Bumped version to 1.9e.
dmouldin
More... over 17 years ago
Bumped version to 1.9e. Removed cautions that are no longer applicable from comments.
dmouldin
More... over 17 years ago
Changed instructions for copying the dbghelp.dll private assembly when building from source, given that it is no longer deployed in its own subdirectory. Added mscvr80.dll to legal jargon in the License section.
dmouldin
More... over 17 years ago
More additions for the 1.9e release.
dmouldin
More... over 17 years ago
Added locking needed to protect Iterators from becoming invalidated due to other threads simultaneously deleting elements from the Tree.
db
More... over 17 years ago
Updated for the 1.9e release.
db
More... over 17 years ago
Bumped revision up to 1.9d(p1). Added installer/uninstaller steps for installing dbghelp.dll as a private assembly.
dmouldin
More... over 17 years ago
Increased default number of threads to 72.
dmouldin
More... over 17 years ago
Added some intermediate notes prior to the 1.9e release. These may change.
dmouldin
More... over 17 years ago
Pointed the Release configuration at the correct additional manifest file for using dbghelp.dll as a private assembly.
dmouldin
More... over 17 years ago
Switched back to load-time linking with dbghelp.dll. Runtime dynamic linking turns out to have been a bad idea because dbghelp.dll is detached from the process before the VLD destructor is called, so the dbghelp.dll functions used in the destructor (in particular symbol lookups during dumping of callstacks) were being called after dbghelp.dll had already cleaned up internal resources. The solution is to embed the appropriate information in the manifest required to use dbghelp.dll as a private assembly, and then create a private assembly manifest for dbghelp.dll.
dmouldin
More... over 17 years ago
Switched back to load-time linking with dbghelp.dll. Runtime dynamic linking turns out to have been a bad idea because dbghelp.dll is detached from the process before the VLD destructor is called, so the dbghelp.dll functions used in the destructor (in particular symbol lookups during dumping of callstacks) were being called after dbghelp.dll had already cleaned up internal resources. The solution is to embed the appropriate information in the manifest required to use dbghelp.dll as a private assembly, and then create a private assembly manifest for dbghelp.dll.
dmouldin
More... over 17 years ago
Switched back to load-time linking with dbghelp.dll. Runtime dynamic linking turns out to have been a bad idea because dbghelp.dll is detached from the process before the VLD destructor is called, so the dbghelp.dll functions used in the destructor (in particular symbol lookups during dumping of callstacks) were being called after dbghelp.dll had already cleaned up internal resources. The solution is to embed the appropriate information in the manifest required to use dbghelp.dll as a private assembly, and then create a private assembly manifest for dbghelp.dll.
dmouldin
More... over 17 years ago
Switched back to load-time linking with dbghelp.dll. Runtime dynamic linking turns out to have been a bad idea because dbghelp.dll is detached from the process before the VLD destructor is called, so the dbghelp.dll functions used in the destructor (in particular symbol lookups during dumping of callstacks) were being called after dbghelp.dll had already cleaned up internal resources. The solution is to embed the appropriate information in the manifest required to use dbghelp.dll as a private assembly, and then create a private assembly manifest for dbghelp.dll.
dmouldin
More... over 17 years ago
Switched back to load-time linking with dbghelp.dll. Runtime dynamic linking turns out to have been a bad idea because dbghelp.dll is detached from the process before the VLD destructor is called, so the dbghelp.dll functions used in the destructor (in particular symbol lookups during dumping of callstacks) were being called after dbghelp.dll had already cleaned up internal resources. The solution is to embed the appropriate information in the manifest required to use dbghelp.dll as a private assembly, and then create a private assembly manifest for dbghelp.dll.
dmouldin
More... over 17 years ago
Changed the locking strategy from, "lock as liberally as possible to avoid potential race conditions" to "lock as sparingly as possible to avoid deadlocks".
dmouldin
More... over 17 years ago