A modern, browser-based frontend to gdb (gnu debugger). Add breakpoints, view stack traces, and more in C, C++, Go, and Rust! Simply run gdbgui from the terminal and a new tab will open in your browser. Screenshots are below.
sudo pip install gdbgui --upgrade
sudo pip install gdbgui --upgrade --user
Follow these instructions to codesign gdb if you get an error such as please check gdb is codesigned - see taskgated(8)
Tested with cygwin. If you have run this natively, contact me and let me know so I can update this section.
pip install gdbgui --upgrade
virtualenv users do not need the sudo prefix.
Alternatively, you can clone and run directly
git clone https://github.com/cs01/gdbgui cd gdbgui pip install -r requirements.txt gdbgui/backend.py
gdbgui [binary to debug]
A new tab in your browser will open with gdbgui in it.
Debug a different program in each tab (new gdb instance is spawned for each tab)
View stack, threads
Switch frame on stack, switch between threads
Intuitively explore local variables when paused
Evaluate arbitrary expressions and plot their values over time
Inspect memory in hex/character form
View all registers
Dropdown of all files used to compile binary, with autocomplete functionality
Source code explorer with ability to jump to line
Show assembly next to source code, highlighting current instruction. Can also step through instructions.
Notifications when new updates are available
Actively developed and compatible with the latest version of gdb (7.12)
Does only one thing: debugs programs. No integrated build system, no project settings, nothing to make things more complicated than they need to be. Just a lightweight frontend.
Design influenced by the amazing Chrome debugger
Full gdb command line utility built-in
Open source and free
Example code and makefiles for C, C++, go, and rust, that build and launch gdb.
See the examples folder.
- Positional arguments:
command: (Optional) The executable and arguments to run in gdb. This is a way to script the intial loading of the inferior program you wish to debug. For example gdbgui "./mybinary -myarg -flag1 -flag2" (note the quotes around the executable and arguments). Executables and arguments can also be input through the browser interface after launching (no quotes required there).
- Flags (all are optional):
- -h, --help
show this help message and exit
- -p PORT, --port PORT
The port on which gdbgui will be hosted
- --host HOST
The host ip address on which gdbgui serve.
- -r, --remote
Shortcut to sets host to 0.0.0.0 and suppress browser from opening. This allows remote access to gdbgui and is useful when running on a remote machine that you want to view/debug from your local browser, or let someone else debug your application remotely.
- -g GDB, --gdb GDB
Path to gdb executable or lldb-mi executable. Defaults is ‘gdb’. lldb support is experimental and not fully functional at this time.
- -v, --version
The debug flag of this Flask application. Pass this flag when debugging gdbgui itself to automatically reload the server when changes are detected
- -n, --no_browser
By default, the browser will open with gdb gui. Pass this flag so the browser does not open.
Python versions: 2.7, 3.4, 3.5, 3.6, 3.6-dev, 3.7-dev, pypy
Operating systems: Ubuntu 14.04+, OSX
Browsers: Chrome, Firefox
Gdb: 7.7.1 and 7.12 were tested. Likely works with intermediate versions.
Help the gdbgui project grow by spreading the word. The more people who use it, the better it gets.
Creating and voting on issues in github will help me prioritize what to work on.
Documentation, spelling fixes, bug fixes, features, etc. are of course welcome too. To get started with development, set up a new virtual environment, then run
git clone https://github.com/cs01/gdbgui cd gdbgui pip install -r requirements.txt pip install -r dev_requirements.txt gdbgui/backend.py --debug
If you are modifying gdbgui.js, make sure you have the developer console open so the browser doesn’t cache the file and miss your changes. When --debug is passed, there is a new component at the bottom of the right sidebar that displays the raw gdb mi output to help you debug.
make test runs unit tests and verifies README.rst is properly formatted. gdbgui/tests/test_app.py. Add new tests there as necessary.
pyPI and this github page are the only official sources of gdbgui.
How Does it Work?
It uses Python to manage gdb as a subprocess. Specifically, the pygdbmi library, which returns key/value pairs (dictionaries) that can be used to create a frontend. To make a usable frontend, first a server must made to interface with gdb. In this case, the Flask server is used, which does three things: creates a managed gdb subprocess with pygdbmi, spawns a separate thread to constantly check for output from the gdb subprocess, and creates endpoints for the browser including http requests and websocket connections.
As output is parsed in the reader thread, it is immediately sent to the frontend through the websocket. As the browser receives these websocket messages, it maintains the state of gdb (whether it’s running, paused, or exited, where breakpoints are, what the stack is, etc.) and updates the DOM as appropriate. The browser also sends commands to gdb through a websocket to Flask server, which then passes the command to gdb. Gdb writes new output, which is picked up by the reader thread.
gdbgui was designed to be easily hackable and extendable. There is no build system necessary to run or develop this app.
The main components of gdbgui are
gdbgui.pug: HTML file that defines the frontend
gdbgui.js: The majority of the application is contained in this file. It dynamically updates the page, and maintains gdb state. It sends AJAX requests and uses websockets to interact with gdb through the server, then gets the response and updates the DOM as necessary.
gdbgui.css: css stylesheet
Enter the binary and args just as you’d call them on the command line. Binary is restored when gdbgui is opened at a later time.
Intuitive control of your program. From left to right: Run, Continue, Next, Step, Return, Next Instruction, Step Instruction, send interrupt signal (SIGINT) to inferior process.
View all threads, the full stack on the active thread, the current frame on inactive threads. Switch between frames on the stack, or threads by pointing and clicking.
View source, assembly, add breakpoints. All symbols used to compile the target are listed in a dropdown above the source code viewer, and have autocompletion capabilities.
With assembly. Note the bold line is the current instruction that gdb is stopped on.
Variables and Expressions
All local variables are automatically displayed, and are clickable to explore their fields.
Arbitrary expressions can be evaluated as well.
Expressions record their previous values, and can be displayed in an x/y plot.
All hex addresses are automatically converted to clickable links to explore memory. Length of memory is configurable. In this case 16 bytes are displayed per row.
View all registers. If a register was updated it is highlighted in yellow.
Read gdb output, and write to the gdb subprocess as desired. Don’t let any gdb commandline skills you’ve developed go to waste.
gdbgui at launch:
Release history Release notifications | RSS feed
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.