| Part of a series on |
| Software development |
|---|
Paradigms and models |
Standards and bodies of knowledge |
 | This articleneeds additional citations forverification. Please helpimprove this article byadding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Debugger" – news ·newspapers ·books ·scholar ·JSTOR(January 2026) (Learn how and when to remove this message) |
Adebugger issoftware forexecuting acomputer program in an environment that allows for programming-level inspection and control. A debugger is often used todebug, but can be used for other goals including testing. Common features of a debugger includestepping through code line-by-line, breaking into the program's flow of control, managingbreakpoints, and reporting and modifying memory.
Asource-level debugger (a.k.a.symbolic debugger) provides auser experience that integrates the program'ssource code. Typically, such a debugger can indicate which line of source code corresponds to the execution point of the program and allows for reading and writing memory via the symbols of the source code. In contrast, alow-level debugger (a.k.a.machine-language debugger) shows the execution point asmachine code or its associatedassembly language and allows memory access by address only.
The code to be examined might alternatively be running on aninstruction 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.
Typically, debuggers offer a query processor, a symbol resolver, an expression interpreter, and a debug support interface at its top level.[1] Debuggers also offer more sophisticated functions such as running a program step by step (single-stepping orprogram animation), stopping (breaking) (pausing the program to examine the current state) at some event or specified instruction by means of abreakpoint, and tracking the values of variables.[2]Some debuggers have the ability to modify the program state while it is running. It may also be possible to continue execution at a different location in the program to bypass a crash or logical error.
The same functionality which makes a debugger useful for correcting bugs allows it to be used as asoftware cracking tool to evadecopy protection,digital rights management, and other software protection features. It often also makes it useful as a general verification tool,fault coverage, andperformance analyser, especially ifinstruction path lengths are shown.[3]
Most mainstream debugging engines, such asgdb anddbx, provide console-basedcommand line interfaces.Debugger front-ends are popular extensions to debugger engines that provideIDE integration, program animation, and visualization features.
If a program is running with a debugger, and anexception occurs because of aprogramming bug or invalid data, the debugger is notified of the exception. When the program "traps" or reaches a preset condition, the debugger typically shows the location in the original code if it is a source-level debugger or symbolic debugger. If it is a low-level debugger or a machine-language debugger it shows the line in thedisassembly (unless it also has online access to the original source code and can display the appropriate section of code from the assembly or compilation).
Record and replay debugging,[4] also known as "software flight recording" or "program execution recording", captures application state changes and stores them to disk as each instruction in a program executes. The recording can then be replayed and interactively debugged to diagnose and resolve defects. Record and replay debugging is useful for remote debugging and for resolving intermittent, non-deterministic, and other hard-to-reproduce defects.
Some debuggers include a feature called "reverse debugging", also known as "historical debugging" or "backwards debugging". These debuggers make it possible to step a program's execution backwards in time. Various debuggers include this feature.Microsoft Visual Studio (2010 Ultimate edition, 2012 Ultimate, 2013 Ultimate, and 2015 Enterprise edition) offers IntelliTrace reverse debugging for C#, Visual Basic .NET, and some other languages, but not C++. Reverse debuggers also exist for C, C++, Java, Python, Perl, and other languages. Some are open source; some are proprietary commercial software. Some reverse debuggers slow down the target by orders of magnitude, but the best reverse debuggers cause a slowdown of 2× or less. Reverse debugging is very useful for certain types of problems, but is not commonly used.[5]
In addition to the features of reverse debuggers,time travel debugging also allow users to interact with the program, changing the history if desired, and watch how the program responds.
Some debuggers operate on a single specific language while others can handle multiple languages transparently. For example, if the main target program is written inCOBOL but callsassembly language subroutines andPL/1 subroutines, the debugger may have to dynamically switch modes to accommodate the changes in language as they occur.
Some debuggers also incorporate memory protection to avoidstorage violations such asbuffer overflow. This may be extremely important intransaction processing environments where memory is dynamically allocated from memory 'pools' on a task by task basis.
Some processors have hardware support for single-stepping a program, such as thetrap flag.
Most modern microprocessors have at least one of these features in theirCPU design to make debugging easier:
Some of the most capable and popular debuggers implement only a simple command line interface (CLI)—often to maximizeportability and minimize resource consumption. Developers typically consider debugging via agraphical user interface (GUI) easier and more productive.[citation needed] This is the reason for visual front-ends, that allow users to monitor and control subservient CLI-only debuggers viagraphical user interface. Some GUI debugger front-ends are designed to be compatible with a variety of CLI-only debuggers, while others are targeted at one specific debugger.
Debugging is often used to illegally crack or pirate software, which is usually illegal even when done non-maliciously.Crackme's are programs specifically designed to be cracked or debugged. These programs allow those with debuggers to practice their debugging ability without getting into legal trouble.
