Browser-based frontend to gdb (gnu debugger). Add breakpoints, view the stack, visualize data structures, and more in C, C++, Go, Rust, and Fortran. Run gdbgui from the terminal and a new tab will open in your browser.
Full Changelog: https://github.com/cs01/gdbgui/compare/v0.15.1.0...0.15.2.0
--rr
does not exist anymore) by @gs0-pix4d in https://github.com/cs01/gdbgui/pull/415
Full Changelog: https://github.com/cs01/gdbgui/compare/v0.15.0.1...v0.15.1.0
This release has no changes to features or usability. The only change is to include a file used by other package maintainers.
This release is focused mostly on Python 3.9 compatibility and updating dependencies
set pagination on
.This release works for all operating systems, including Windows.
ImportError: cannot import name 'NoGdbProcessError'
by pinning dependencies to ensure they are all compatible. Note that this means the only way gdbgui should be run is by installing inside a virtual environment, installing with pipx (as it uses virtual environments), or to run the executable build from gdbgui's release page.--gdb
flag was removedReplaced single terminal on frontend with three terminals: an interactive xterm terminal running gdb, a gdbgui console for diagnostic messages, and a terminal connected to the inferior application being debugged. The gdb process that runs is now connected to a terminal you control directly. Everything works as expected -- tab completion, ctrl+c (break), and gdb will wait for user input. This differs from previous behavior when gdb was run as a subprocess and was not connected to a terminal.
Breaking Changes
--gdb
flag with --gdb-cmd
. The --gdb-cmd
argument specifies the gdb executable as well as all arguments you wish to pass to gdb at startup, for example --gdb-cmd "gdb -nx"
. The existing -g
argument is an alias for --gdb-cmd
.--rr
flag. Use --gdb-cmd rr replay
instead.--hide-gdbgui-upgrades
argument. It will now raise an error.Additional Changes
A test release for major changes to gdbgui. This release drops support for Windows.