Erlang Debugger
erlang.org
- Windows
- macOS
- Linux
What Erlang Debugger is
Erlang Debugger is a free, open-source graphical interface for debugging and testing Erlang programs on Windows, macOS, and Linux. Developers can set line, conditional, and function breakpoints, attach to processes, and step, continue, finish, skip, or stop execution. The Attach Process window displays variable bindings and permits editing values when the running system can represent them. A Monitor window shows interpreted modules and process information. Debugger can record interpreted calls for stack navigation, while tail-call recording uses more memory and can slow heavily recursive programs. Modules need debug information, such as compilation with `erlc +debug_info`. Remote nodes are supported through global mode. Interpreted code runs slower, each debugged process adds a meta process, timers may behave differently, and code replacement does not work for debugged processes.
Who it suits
It is intended for people familiar with Erlang who need graphical debugging on Windows, macOS, or Linux. Remote debugging and conditional breakpoints suit distributed or selective investigation.
Good to know, and what to watch
- Free and open source
- Line, conditional, and function breakpoints
- Remote-node debugging support
- Process variable inspection and editing
- Graphical process monitoring
- Requires modules compiled with debug information
- Interpreted code runs slower
- Each debugged process adds a meta process
- Timers can behave differently while debugging
The verdict
Erlang Debugger covers core interactive debugging tasks, including process control, breakpoints, inspection, and remote nodes. Its interpreted runtime and process-related limitations matter when debugging timing-sensitive or performance-heavy applications.
What the maker publishes
- Breakpoints
- It supports line, conditional, and function breakpoints. source
- Breakpoints
- It supports line, conditional, and function breakpoints; when a process reaches a breakpoint, it pauses for commands such as step, skip, or continue. source
- Code loading
- Reinterpreting a module does not change the code version used by processes already executing the previous interpreted version. source
- Code replacement limitation
- Code replacement does not work for debugged processes because they use code stored when their modules were interpreted. source
- Distribution
- The Erlang/OTP download page offers source builds, Windows installers, and package-manager instructions for macOS and several Linux distributions. source
- Inspect variables
- The Attach Process window displays variable bindings and allows editing values, with some runtime values not editable unless representable in the running system. source
- Intended users
- The introduction assumes readers are familiar with the Erlang programming language. source
- License
- Erlang/OTP releases from version 18.0 onward use the Apache License 2.0. source
- License
- Erlang/OTP has been released under Apache License 2.0 since OTP 18.0. source
- Maintainer
- The Erlang/OTP unit at Ericsson is the main developer and maintainer of Erlang/OTP. source
- Performance
- Interpreted code runs slower than regularly compiled modules, and Debugger creates an additional meta process for each debugged process. source
- Performance limit
- Interpreted code runs more slowly than regularly compiled code, and each debugged process adds a meta process. source
- Prerequisite
- Modules to debug must include debug information, for example by compiling with `erlc +debug_info`. source
- Prerequisite
- Modules to be debugged must be compiled with debug information enabled. source
- Process controls
- When attached to a process, users can step, continue, finish, skip, or stop its execution. source
- Process inspection
- Attaching to a process lets the user control execution, inspect variable values, and set breakpoints. source
- Process monitoring
- The Monitor window displays interpreted modules and information about processes executing interpreted code. source
- Purpose
- Debugger is a graphical interface for debugging and testing Erlang programs. source
- Purpose
- Erlang Debugger is a graphical interface for the Erlang interpreter used to debug and test Erlang programs. source
- Remote nodes
- In global mode, Debugger interprets code on known nodes and displays processes from those nodes; the documentation warns against running global mode on multiple nodes in a network because they can interfere. source
- Remote nodes
- Global mode interprets code on all known Erlang nodes and displays eligible processes from other nodes for attachment. source
- Stack trace
- Debugger can record interpreted function calls for stack navigation, and recording tail calls uses more memory and slows execution when there are many tail-recursive calls. source
- Supported interpreter dependencies
- The interpreter depends on the Kernel, STDLIB, and WX applications, and modules in those applications or Debugger cannot be interpreted. source
- Timer behavior
- Programs with timers can behave differently during debugging, especially when a process is stopped while other processes continue running. source
Checked against the maker's pages on 9 Oct 2026.