enow.com Web Search

Search results

  1. Results from the WOW.Com Content Network
  2. List of performance analysis tools - Wikipedia

    en.wikipedia.org/wiki/List_of_performance...

    64-bit and 32-bit applications, C, C++, .NET, and dlls generated by any language compiler. Performance and memory profiler that identifies time-intensive functions and detects memory leaks and errors. Proprietary gprof: Linux/Unix Any language supported by gcc: Several tools with combined sampling and call-graph profiling.

  3. PurifyPlus - Wikipedia

    en.wikipedia.org/wiki/PurifyPlus

    The ability to detect non-fatal errors is a major distinction between PurifyPlus and similar programs from the usual debuggers.By contrast, debuggers generally only allow the programmer to quickly find the sources of fatal errors, such as a program crash due to dereferencing a null pointer, but do not help to detect the non-fatal memory errors.

  4. Boehm garbage collector - Wikipedia

    en.wikipedia.org/wiki/Boehm_garbage_collector

    In this way a programmer can find memory leaks and double deallocations. Boehm GC is also distributed with a C string handling library called cords. This is similar to ropes in C++ ( trees of constant small arrays), but instead of using reference counting for proper deallocation, it relies on garbage collection to free objects.

  5. Cppcheck - Wikipedia

    en.wikipedia.org/wiki/Cppcheck

    Cppcheck is a static code analysis tool for the C and C++ programming languages. It is a versatile tool that can check non-standard code. [2] The creator and lead developer is Daniel Marjamäki. Cppcheck is free software under the GNU General Public License.

  6. Memory leak - Wikipedia

    en.wikipedia.org/wiki/Memory_leak

    The "sawtooth" pattern of memory utilization: the sudden drop in used memory is a candidate symptom for a memory leak. If the memory leak is in the kernel, the operating system itself will likely fail. Computers without sophisticated memory management, such as embedded systems, may also completely fail from a persistent memory leak.

  7. Memory debugger - Wikipedia

    en.wikipedia.org/wiki/Memory_debugger

    A memory debugger is a debugger for finding software memory problems such as memory leaks and buffer overflows. These are due to bugs related to the allocation and deallocation of dynamic memory . Programs written in languages that have garbage collection , such as managed code , might also need memory debuggers, e.g. for memory leaks due to ...

  8. BoundsChecker - Wikipedia

    en.wikipedia.org/wiki/BoundsChecker

    BoundsChecker is a memory checking and API call validation tool used for C++ software development with Microsoft Visual C++.It was created by NuMega in the early 1990s. When NuMega was purchased by Compuware in 1997, BoundsChecker became part of a larger tool suite, DevPartner Studio.

  9. CHKDSK - Wikipedia

    en.wikipedia.org/wiki/CHKDSK

    CHKDSK is implemented as an external command. MS-DOS versions 2.x - 4.x use chkdsk.com as the executable file. MS-DOS versions 5.x and later use chkdsk.exe as the executable file. [8] CHKDSK can also show the memory usage, this was used before the command MEM.EXE was introduced in MS-DOS 4.0 to show the