Search Results for "detection"

A cross-platform implementation of a mutex, that automatically checks for everything, you might be doing wrong: - DeadLocks - Invalid mutex leave order - Thread Shutdown, while still holding mutex locks - Destroying a locked mutex - (Un)Locking a destroyed mutex - UnLocking an unlocked mutex - UnLocking an mutex locked by another thread - Locking a non-recursive, locked mutex - Not destroying all mutexes before application termination Every abnormal produces a console output with file and line information about were it is located and why it happened. The main purpose of debug_mutex is the detection of deadlocks and outputting useful information, to fix it, by telling you exactly, where the recursion happened. Debug_mutex can easily be disabled and simply used as a cross-platform mutex Library Debug_mutex can be linked statically or externally

You are searching _CrtDumpMemoryLeaks(), _CrtSetReportMode() and all the well known Win32 stuff? But you don't find it for your Windows CE or Windows Mobile native C or C++ development? Get tired of Memory Leaks? Handle Leaks? Trouble with Appverify (Application Verifier for WinCE)? Stop searching. Congratulations, you got it!

memwatch is an ANSI C fault tolerant memory leak and corruption detection tool. Basically, you add a header file to your souce code files, and compile with MEMWATCH defined or not. Check the README and USING files for more instructions.

...It uses the memory paging system to allocate a guard page after each page of memory to provide a hardware boundary that can detect memory overflows. This allows for immediate detection of buffer overflow error conditions. There are many other memory checker programs in existence - why do we need another? This Hardware Memory Checker provides a combination of features not found in other memory checkers. - it uses the hardware paging system for immediate error detection (most other memory checkers look for modified memory in no mans land) - it is very fast compared to other hardware memory checkers because it makes fewer changes to the paging tables - it can track the original release location when debugging duplicate free problems - it is designed for large scale integration with the ability to call user defined fail functions