|
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 "living" references in collections. Overview Memory debuggers work by monitoring memory access, allocations, and deallocation of memory. Many memory debuggers require applications to be recompiled with special dynamic memory allocation libraries, whose APIs are mostly compatible with conventional dynamic memory allocation libraries, or else use dynamic linking. Electric Fence is such a debugger which debugs memory allocation with malloc. Some memory debuggers (e.g. Valgrind) work by running the executable in a virtual machine-like environment, monitoring memory access, allocation and deallocation so that no recompilation with special memory ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Debugger
A debugger is a computer program used to test and debug other programs (the "target" programs). Common features of debuggers include the ability to run or halt the target program using breakpoints, step through code line by line, and display or modify the contents of memory, CPU registers, and stack frames. The code to be examined might alternatively be running on an '' instruction set simulator'' (ISS), a technique that allows great power in its ability to halt when specific conditions are encountered, but which will typically be somewhat slower than executing the code directly on the appropriate (or the same) processor. Some debuggers offer two modes of operation, full or partial simulation, to limit this impact. An exception occurs when the program cannot normally continue because of a programming bug or invalid data. For example, the program might have tried to use an instruction not available on the current version of the CPU or attempted to access unavailable or pro ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Profiling (computer Programming)
In software engineering, profiling (program profiling, software profiling) is a form of dynamic program analysis that measures, for example, the space (memory) or time complexity of a program, the usage of particular instructions, or the frequency and duration of function calls. Most commonly, profiling information serves to aid program optimization, and more specifically, performance engineering. Profiling is achieved by instrumenting either the program source code or its binary executable form using a tool called a ''profiler'' (or ''code profiler''). Profilers may use a number of different techniques, such as event-based, statistical, instrumented, and simulation methods. Gathering program events Profilers use a wide variety of techniques to collect data, including hardware interrupts, code instrumentation, instruction set simulation, operating system hooks, and performance counters. Use of profilers The output of a profiler may be: * A statistical ''summary ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Dmalloc
Dmalloc is a C memory debugger library written by Gray Watson to assist programmers in finding a variety of dynamic memory allocation mistakes. It replaces parts (such as malloc) of the C standard library provided by the operating system or compiler with its own versions, which produce information intended to help the programmer detect problematic code. Dmalloc can find memory leaks, off-by-one error An off-by-one error or off-by-one bug (known by acronyms OBOE, OBOB, OBO and OB1) is a logic error that involves a number that differs from its intended value by 1. An off-by-one error can sometimes appear in a mathematics, mathematical context. ...s, and usage of invalid addresses in some library functions calls. See also * External links Dmalloc Official web siteDmalloc Github web siteMemory Leak Detection in Embedded Systems Memory management software Free memory debuggers {{unix-stub ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Debug New
{{context, date=February 2020 Debug_new refers to a technique in C++ to overload and/or redefine operator new and operator delete in order to intercept the memory allocation and deallocation calls, and thus debug a program for memory usage. It often involves defining a macro named DEBUG_NEW, and makes new become something like new(__FILE__, __LINE__) to record the file/line information on allocation. Microsoft Visual C++ uses this technique in its Microsoft Foundation Classes. There are some ways to extend this method to avoid using macro redefinition while still able to display the file/line information on some platforms. There are many inherent limitations to this method. It applies only to C++, and cannot catch memory leaks by C functions like malloc. However, it can be very simple to use and also very fast, when compared to some more complete memory debugger solutions. See also *Memory debugger A memory debugger is a debugger for finding software memory problems such a ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Daikon (system)
Daikon is a computer program that detects likely invariants of programs. An invariant is a condition that always holds true at certain points in the program. It is mainly used for debugging programs in late development, or checking modifications to existing code. Properties Daikon can detect properties in C, C++, Java, Perl, and IOA programs, as well as spreadsheet files or other data sources. Daikon is easy to extend and is free software Free software, libre software, libreware sometimes known as freedom-respecting software is computer software distributed open-source license, under terms that allow users to run the software for any purpose as well as to study, change, distribut .... External links DaikonOfficial home site Source Repositoryon GitHub Dynamically Discovering Likely Program Invariants Michael D. Ernst PhD. Thesis (using Daikon) References Free computer programming tools Static program analysis tools Software testing {{programming-software-s ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
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. Micro Focus purchased the product line from Compuware in 2009. Comparable tools include Purify, Insure++ and Valgrind. BoundsChecker may be run in two distinct modes: ActiveCheck, which will work against any application as is, or FinalCheck, which makes use of instrumentation added to the application when it is built. ActiveCheck performs a less intrusive analysis and monitors all calls by the application to the C Runtime Library, Windows API and calls to COM objects. By monitoring memory allocations and releases, it can detect memory leaks and overruns. Monitoring API and COM calls enables ActiveCheck to check parameters, returns and exceptions and report exceptions when they occur. Thre ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Bcheck
In Solaris, bcheck (batch utility for Runtime Checking (RTC)) is a memory access and memory leak checking tool based on dbx. It is commonly used in software development to detect and diagnose memory-related errors in programs. This tool helps developers by identifying issues such as invalid memory accesses, uninitialized memory reads, and memory leaks during the runtime of a program. Additionally, `bcheck` integrates seamlessly with other debugging and profiling tools, making it a versatile choice for comprehensive software Software consists of computer programs that instruct the Execution (computing), execution of a computer. Software also includes design documents and specifications. The history of software is closely tied to the development of digital comput ... analysis. References External linksStudio 12.2 bcheck documentation Debuggers Unix programming tools POSIX {{compu-lang-stub ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
AQtime
AQtime is a performance profiler and memory/resource debugging toolset developed by SmartBear Software. It is integrated into Microsoft Visual Studio, Visual Studio Test Projects, and Embarcadero RAD Studio, which allows analyzing the application without leaving the development environment. Overview AQtime is used for multiple optimization tasks to improve application performance and memory usage. It includes a set of profilers for the analysis of different application aspects. It does sophisticated application performance analysis of function execution time down to the individual source code lines. It tracks performance issues and memory leaks. It analyzes resource usage and function call order. It monitors code coverage, Windows API compliance and includes other profilers for analyzing more application properties. Features * Support for Windows and .NET compilers. * Support for profiling 32- and 64-bit applications. * Profiling Java and Silverlight Applications. * Profiling ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Allinea Distributed Debugging Tool
Linaro DDT is a commercial C, C++ and Fortran 90 debugger. It is widely used for debugging parallel Message Passing Interface (MPI) and threaded (pthread or OpenMP) programs, including those running on clusters of Linux machines. Debugger It is used to find bugs on both small and large clusters, from 1 to 100,000s of processors. It features memory debugging which detect memory leaks, or reading and writing beyond the bounds of arrays. It was the first debugger to be able to debug petascale applications - having been used to debug applications running concurrently on 220,000 processes on a Cray XT5 at Oak Ridge National Laboratories. This is possible interactively as the debugger's control tree architecture leads to logarithmic performance for most collective operations. Linaro DDT uses the GNU Debugger as debug engine. Linaro DDT also supports coprocessor architectures such as Intel Xeon Phi coprocessors and Nvidia CUDA GPUs. It is part of Linaro Forge - a suite of tools f ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
