Debugger

The JavaScript Debugger enables you to step through JavaScript code and examine or modify its state to help track down bugs.

You can use it to debug code running locally in Firefox or running remotely, for example in a Firefox OS device or Firefox on Android. This guide assumes you're debugging locally, but it's mostly applicable to remote debugging as well. See the guide to remote debugging for the differences.

To open the Debugger select "Debugger" from the Web Developer submenu in the Firefox Menu (or Tools menu if you display the menu bar or are on Mac OS X), or by pressing its Control-Shift-S (Command-Option-S on the Mac) keyboard shortcut.

The Toolbox will appear at the bottom of the browser window, with the Debugger activated. Here's what it looks like when you first open it:

And here's what it looks like in the middle of a debugging session:

In this guide we'll first have a quick tour of the debugger's user interface, then we'll describe how to perform some common debugging tasks.

The debugger user interface

The debugger's UI is split into five main sections, which we'll cover one at a time:

Source list pane

The left-hand side of the debugger lists all the JS source files loaded into the page, and enables you to select one to debug.

Source files are grouped under different headings according to where they are loaded from. For example, this is part of the source list pane when a page on developer.mozilla.org is loaded:

This corresponds to the following script tags in the page:

<script src="/en-US/jsi18n/build:8987063"></script>
<script src="https://login.persona.org/include.js" type="text/javascript"></script>
<script src="//mozorg.cdn.mozilla.net/en-US/libs/jquery-1.7.1.min.js" type="text/javascript"></script>
<script src="//mozorg.cdn.mozilla.net/en-US/tabzilla/tabzilla.js" async></script>

You can select any of these files and they will be loaded into the Source pane.

Any breakpoints you've set in a source file are listed in the source list pane under the filename:The check box enables you to enable/disable the breakpoint. Right-clicking on the breakpoint's entry in the list shows a context menu enabling you to:

  • enable, disable or remove this breakpoint, all breakpoints, or all breakpoints except this one
  • make this breakpoint conditional (or edit its conditions, if it is already conditional)

The eyeball at the bottom-left of the pane is a button that enables you to black box the currently selected source. Black boxing is useful for sources which you are using but not debugging, such as libraries like jQuery. If a source is black boxed, it's assumed to be of no interest to the debugger: any breakpoints in it will be disabled, and the debugger will skip through it when stepping through code.

In versions of Firefox before 27, the eyeball icon appears next to the source file name when you hover over it.

Source pane

This shows the JavaScript file currently loaded. Breakpoints have a blue circle next to the line number, while breakpoints you've hit have a green arrow inside the circle:

In the source pane, the context menu enables you to:

  • set a breakpoint
  • set a conditional breakpoint
  • add a watch expression for the selection
  • search or filter using the script filter

Toolbar

The toolbar consists of four sections:

  • a row of buttons to control movement through a script
  • a visualisation of the call stack
  • the script filter
  • buttons to expand/collapse the variables and events panes and to control debugger settings

The four buttons on the left perform the following functions:

  • Pause/Resume (F6): pauses or resumes execution of the script you're debugging. When it's blue and "pressed", as above, that means the script is paused, either because you've paused it with this button or because you've hit a breakpoint.
  • Step Over (F7): steps across the current line of JavaScript code.
  • Step Into (F8): steps into the function call on the current line of JavaScript code.
  • Step Out (Shift-F8): runs the script until the current function exits.

The call stack visualisation shows the call stack at the point execution is paused.

Script filter

The script filter enables you to search in all three of the debugger's panes. By prefixing the filter expression with one of several special characters, the filter provides various different functions.

Prefix Function
None Filter the scripts shown in the source list pane.
! Search for the string across all files.
@ Search for function definitions, across all files, containing the string.
# Search for the string in the file currently open in the source pane.
: Go to the line given in the file currently open in the source pane.
* Filter the variables shown in the variables pane.

These options are shown in a pop-up when you click in the filter, and they're also accessible from the context menu in the source pane. Prefixes can be combined to form more powerful queries, like "file.js:12", which will open file.js and highlight line 12, or "mod#onLoad", which will find the string onLoad in all files containing mod in their name. Hitting the Enter key after searching will cycle between the matches found.

Debugger settings

At the right-hand end of the toolbar are two more buttons. The first of these shows and hides the variables and events panes, and the second enables you to toggle various debugger settings:

Pause on exceptions When this option is enabled, execution of the script will automatically pause whenever a JavaScript exception is thrown.
Ignore caught exceptions

If this option is set (it is set by default) and "Pause on exceptions" is set, then execution will pause on an exception only if that exception is not caught. This is usually the behavior you want (you don't generally want to pause execution when an exception that is thrown is caught, since that generally indicates that your program is handling it properly).

This option is new in Firefox 26.

Show panes on startup When this option is enabled, the debugger's variables pane is visible when you first start the debugger.
Show only enumerable properties Enabling this option adds a "Filter variables" search box to the variables panel, so that you can filter the displayed list of variables.
Show variables filter box Do not display non-enumerable JavaScript properties
Show original sources Enabling this option will make the debugger use source maps, if they are available, to display the original source for code which has been combined, minified, or even compiled to JavaScript from a language like CoffeeScript.

Variables pane

The variables pane is where you can examine, and modify, the internal state of the script as it's executing:

The variables pane shares its screen real estate with the events pane, and you can use the tabs at the top of the pane to switch between them.

Examining variables

Variables are grouped by scope: in Function scope you'll see the built-in arguments and this variables as well as local variables defined by the function like user and greeting. Similarly, in Global scope you'll see global variables you've defined, like greetme, as well as built-in globals like localStorage and console.

Each object can be expanded using a disclosure triangle to show its members.

Pointing your cursor at a variable's name displays a tooltip that provides additional information about the variable; for example, pointing at the greeting object displays "configurable enumerable writable". See Object.defineProperty() for details on what these property descriptors mean.

You can filter the variables that are displayed, either by using the "*" modifier in the script filter, or by typing into the filter variables box, if you have enabled this in the debugger settings.

Modifying variables

You can change a variable's value by clicking on its current value and entering a new one; for example, if you click on "Hi, Dr. Nick!" next to greeting, you can edit the value.

Watch expressions

Watch expressions are expressions that are evaluated each time execution pauses. You can then examine the results of these expressions. These are useful in that they let you inspect invariants in your code that you know are there but aren't necessarily in the code ready for inspection. To add a watch expression, click in the box that says "Add watch expression" and enter a JavaScript expression whose output you'd like to monitor as you step through code.

Then start running your code. The watch expression does nothing until you begin to step through your code, so nothing happens until you reach a breakpoint. At that point, a box showing your active watch expressions and their current values will appear:

You can step through your code, watching the value of the expression as it changes; each time it does, the box will flash briefly yellow. You can remove a watch expression by clicking the "x" icon next to it, and, of course, you can have more than one watch expression at a time.

Events pane

The events pane is new in Firefox 27.

The events pane lists all DOM events that currently have listeners bound from your code:

It shares its screen real estate with the variables pane, and you can use the tabs at the top of the pane to switch between them.

It groups events by type. The screenshot above shows four types: Interaction, Keyboard, Mouse, and Navigation. Under each type it lists all events which have listeners in your code, with the following syntax:

[event name] on [event target] in [source file]

If you check the checkbox next to the event, the debugger will break at the first line of the event's listener. If you check the checkbox next to the event type, then the debugger will break for any of the events listed under that type.

How do I...?

Open the debugger

To open the debugger, select "Debugger" from the Web Developer submenu in the Firefox Menu (or Tools menu if you display the menu bar or are on Mac OS X), or press Control-Shift-S (Command-Option-S on the Mac).

Find a source file

When the debugger's open, all the JavaScript source files are listed in the source list pane. You can browse the list to find the one you want, or search for a particular file using the script filter.

Find inside a file

To find a function, search for a string, or jump to a line in a file open in the source pane, you can use one of the special modifiers in the script filter.

Set a breakpoint

To set a breakpoint in a file open in the source pane:

  • either click on the line number for the line you want to break at
  • or activate the context menu while on the line you want to break at, and select "Add breakpoint"

Each breakpoint is shown in two places in the debugger:

  • they're listed in the source list pane underneath the file's name
  • the line in the source pane is marked with a blue circle

The screenshot below shows breakpoints at lines 10 and 17 of the file:

Set a conditional breakpoint

To set a conditional breakpoint, activate the context menu while on the line you want to break at, and select "Add conditional breakpoint". Then enter the conditional expression in the popup that appears:

To edit the condition, or to add a condition to a normal breakpoint, activate the context menu and select "Configure conditional breakpoint":

Disable a breakpoint

To disable a breakpoint:

  • either: uncheck the check box next to the breakpoint's entry in the source list pane
  • or: activate the context menu while your mouse pointer is over the breakpoint's entry in the source list pane, and select "Disable breakpoint"

Break on a DOM event

This feature is new in Firefox 27.

If you're listening to a particular DOM event, you can tell the debugger to break when the event is triggered without having to track down the listener and set a breakpont manually.

First, open the events pane: click the button in the toolbar that opens the shared variables/events pane, then click the tab labeled "Events". The events pane will list all events for which you have assigned a listener:

Then check the box next to the event you want to break at.

When the event is triggered the code will break at the start of your listener.

Step through my code

When your code stops at a breakpoint, you can step through it using the four buttons on the left of the toolbar:

In order, the buttons are:

  • Play: run to the next breakpoint
  • Step over: advance to the next line in the same function.
  • Step into: advance to the next line in the function, unless on a function call, in which case enter the function being called
  • Step out: run to the end of the current function

Use a source map

JavaScript sources are often combined and minified to make delivering them from the server more efficient. Increasingly, too, JavaScript running in a page is machine-generated, as when compiled from a language like CoffeeScript. By using source maps, the debugger can map the code being executed to the original source files, making debugging much, much easier.

To tell the Debugger to use source maps if they are available, click the "Debugger settings" button and select "Show original sources" from the list of settings that pops up:

Of course, for this to work, you will need to have supplied a source map for the JavaScript running in the page. Do this by appending a comment directive to your source file:

//@ sourceMappingURL=http://example.com/path/to/your/sourcemap.map

Examine variables

When the code has stopped at a breakpoint, you can examine its state in the variables pane of the debugger:

Variables in global scope and in function, block, "with" scopes, etc. are listed separately, and you can expand objects to see their properties. You can also filter the variables shown using the "*" prefix in the script filter:

Modify variables

When the code has stopped at a breakpoint, you can modify variables in the variables pane of the debugger. Just click on the variable's current value and you'll be able to type there:

Watch an expression

You can watch the value of a JavaScript expression using the "Add watch expression" function in the variables pane.

Debug mobile devices

To learn how to debug mobile devices, see the guide to remote debugging.

Black box a source

In modern web development, we often rely on libraries like jQuery, Ember, or Angular, and 99% of the time we can safely assume that they “just work”. We don’t care about the internal implementation of these libraries: we treat them like a black box. However, a library’s abstraction leaks during debugging sessions when you are forced to step through its stack frames in order to reach your own code. With black boxing, you can tell the debugger to ignore the details of selected sources.

In versions of Firefox before Firefox 27, you can black box a source by clicking the eyeball icon next to the source in the source list pane:

From Firefox 27 onwards, enable or disable black boxing for a source by selecting the source in the source list pane and clicking the eyeball icon at the bottom left:

You can black box several sources at once by opening the developer toolbar and using the dbg blackbox command:

When a source is black boxed:

  • Any breakpoints it may have are disabled.
  • When “pause on exceptions” is enabled, the debugger won’t pause when an exception is thrown in the black boxed source; instead it will wait until (and if) the stack unwinds to a frame in a source that isn’t black boxed.
  • The debugger will skip through black boxed sources when stepping.

Access debugging in add-ons

The following items are accessible in the context of chrome://browser/content/debugger.xul (or, in version 23 beta, chrome://browser/content/devtools/debugger.xul):

  • window.addEventListener("Debugger:EditorLoaded") - called when the read-only script panel loaded.
  • window.addEventListener("Debugger:EditorUnloaded")

Relevant files:

  • chrome://browser/content/devtools/debugger-controller.js
  • chrome://browser/content/devtools/debugger-toolbar.js
  • chrome://browser/content/devtools/debugger-view.js
  • chrome://browser/content/devtools/debugger-panes.js

Unfortunately there is not yet any API to evaluate watches/expressions within the debugged scope, or highlight elements on the page that are referenced as variables in the debugged scope. (currently a work in progress, see bug 653545.)

Attachments

File Size Date Attached by
debugger-source-list-pane-only
99839 bytes 2013-08-22 12:59:31 wbamberg
debugger-blackbox-command
17943 bytes 2013-08-26 02:28:22 jryans
debugger-ui-sections
252721 bytes 2013-10-30 20:10:35 wbamberg
debugger-startup
185247 bytes 2013-10-31 10:56:27 wbamberg
debugger-breakpoint-hit
235812 bytes 2013-10-31 10:58:44 wbamberg
debugger-source-list
153111 bytes 2013-10-31 11:14:06 wbamberg
debugger-breakpoint-list-annotated
197330 bytes 2013-11-01 13:02:35 wbamberg
debugger-breakpoint-hit-annotated
254903 bytes 2013-11-01 13:14:04 wbamberg
debugger-toolbar-annotated
204717 bytes 2013-11-01 13:42:08 wbamberg
debugger-variables-pane
244607 bytes 2013-11-01 13:57:39 wbamberg
debugger-watch
223850 bytes 2013-11-01 14:02:06 wbamberg
debugger-events-pane
231570 bytes 2013-11-01 14:53:36 wbamberg
debugger-breakpoint-set-annotated
151732 bytes 2013-11-01 15:26:03 wbamberg
debugger-conditional-breakpoint
129949 bytes 2013-11-01 15:30:36 wbamberg
debugger-conf
143444 bytes 2013-11-01 15:33:05 wbamberg
debugger-stepping-through
191528 bytes 2013-11-01 16:22:47 wbamberg
debugger-show-original-sources
200500 bytes 2013-11-01 16:27:46 wbamberg
debugger-filter-variables
214129 bytes 2013-11-01 16:32:43 wbamberg
debugger-modify-variable
201811 bytes 2013-11-01 16:36:06 wbamberg
debugger-black-box
224286 bytes 2013-11-01 16:54:46 wbamberg
debugger-black-box-fx26
190456 bytes 2013-11-01 17:23:03 wbamberg

Document Tags and Contributors

Contributors to this page: farouk12002
Last updated by: farouk12002,