debugger

advancedwidespread

A debugger is a debugging tool with which a developer can run another program step by step and observe what happens inside it.

In plain terms

If a program malfunctions, you only see the final result from the outside: a wrong number comes out, it freezes, or it throws an error message. The debugger then looks under the hood: it stops the program where you request and shows you what it is doing right now.

It is like a video referee reviewing a disputed scene frame by frame in slow motion. At normal speed, the error is not visible, but when frozen, it precisely reveals the exact moment things went wrong.

It does not fix the bug, nor does it find it for you. It only makes visible what is happening inside the program; the developer, or increasingly a coding agent, must draw the conclusion.

It differs from simple trial and error in that you do not need to guess: it shows the program's actual state, line by line.

How it works

The developer marks a line in the code where the program must stop. This is called a breakpoint.
It starts the program under the debugger's supervision, and the program stops at the marked line as if the pause button had been pressed.
When stopped, you can see the current values of the variables, i.e., the program's "memory," and the path it took to reach this point during execution.
From here, you can step through the program line by line and see at which step reality diverges from what you expected.
Once the faulty step is identified, it corrects the code and reruns the program to verify whether the error is truly resolved.

An everyday example

An online store's cart shows the wrong total if you also redeem a coupon. The developer uses the debugger to pause the program at the discount calculation and sees that the system deducted the same coupon twice. All you notice is that by the next day the price is right.

Who is affected

developerIt is an everyday working tool that helps find the cause of an error much faster than reading the code alone. → Code

parent, student, teacherAnyone learning to program can use a debugger to truly understand how the machine executes, step by step, what they wrote. → Education & Family

entrepreneur, executiveIt helps explain why finding a bug can take longer than fixing it, and where developer time goes in such cases.

everyoneSuch tools mostly detect bugs in applications running on your phone and computer before the update reaches you.

A common misconception

MythA debugger automatically finds and fixes bugs in the program.

In realityA debugger only shows what is happening inside the program. The developer or a coding agent must identify the cause of the error and write the fix.

Limits and risks

You only see the bug that manifests: if a bug occurs rarely or only under heavy load, it is difficult to catch.
Stopping changes the timing, so bugs in programs running on multiple threads simultaneously sometimes disappear or behave differently under a debugger.
Live systems serving customers are not usually stopped with a debugger. Instead, teams work from logs and measurements, using at most tools that take snapshots of the program's state without stopping it.
You cannot peer into the "thinking" of language models: a traditional debugger follows code execution but does not show why the model gave a specific answer.

Similar, but not the same

logging – In logging, the program writes out what happened while running, which you read later, whereas with a debugger you stop and examine it live.
testing – The test shows whether an error exists, while the debugger helps determine where and why it occurred.
linter – The linter flags suspicious parts by reviewing the code text without running it, while the debugger monitors the running program.

Related concepts

Broader

development tool, debugging, software development

Narrower

breakpoint, stepping, Call stack

On the edge

logging, testing, development environment, coding agent, programhiba

A brief history

The word 'bug' was used for technical faults as early as the 19th century, for example by Thomas Edison. The most famous anecdote dates from September 1947: a stuck moth was removed from a relay of the Harvard Mark II computer and taped into the logbook with the note that this was the first case of finding a real 'bug'. One of the most widely used debuggers today, GDB, was started by Richard Stallman in 1986.

Where things stand

The debugger is a built-in part of every serious development environment and browser. By the end of 2026, coding agents increasingly use it on their own too, but the basic principle of debugging has been the same for decades.

Status: 2026 November

In the news

Appears in 14 Agent Age stories; the curve shows weekly occurrence in the news magazine.

Survey: 67% of developers use AI for code generation, 61% for debugging, only 20% in productionNov 7, 2026 · Code
New GEO and AI visibility tools launch: OptimizeGEO, Keytomic, Heading, Yext–Flamel.aiNov 2, 2026 · Marketing
Developers use AI agents to strip ads and trackers from smart TVsOct 19, 2026 · Code
Character.AI bankruptcy and Disney deal open a new phase in chatbot lawsuitsOct 19, 2026 · Jog
Third-party Google rank trackers not fully working, as Search Console still shows rank dataOct 12, 2026 · Marketing
Survey: AI-generated code shifts the bottleneck to debugging, slowing releasesOct 7, 2026 · Code
Nuclear power for data centers: big tech's SMR deals and the existing fleetOct 1, 2026 · Ipar
Undo research: AI agents push debugging to 42% of the workweekSep 29, 2026 · Code

Also known as

debugger · debugger · debugger · tracker · debugging tool · debugging tool · debug · debugging

Sources

This entry was machine-edited and has undergone machine expert review; the “In the news” section updates automatically from Agent Age stories.