A modular visual interface for GDB that displays program state information to reduce debugging commands.
GDB dashboard is a visual interface for the GNU Debugger (GDB) that displays program debugging information in a modular layout. It reduces the need for manual GDB commands by automatically showing relevant data like registers, stack traces, and source code when the program stops. The tool is implemented as a standalone `.gdbinit` configuration file using GDB's Python API.
Developers and software engineers who use GDB for debugging C, C++, or other compiled languages and want a more visual, streamlined debugging workflow without leaving the command-line interface.
It provides immediate visual feedback about program state without modifying GDB's core functionality, allowing developers to debug more efficiently while maintaining full compatibility with standard GDB commands and workflows.
Modular visual interface for GDB in Python
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides a customizable layout showing registers, stack, memory, and source code simultaneously, reducing the need for repetitive GDB commands like 'info registers' or 'backtrace'.
Implemented as a standalone '.gdbinit' file without overriding any GDB commands, ensuring full compatibility with standard debugging workflows and existing scripts.
The dashboard appears automatically whenever the debugged program stops, offering immediate visual feedback on program state without manual intervention.
Optional integration with Pygments allows for enhanced code readability in the source view, improving debugging clarity if Pygments is installed.
Requires GDB with enabled Python API and optionally Pygments, which may not be available in all distributions or restricted environments, limiting portability.
Despite the visual layout, it remains text-based and lacks graphical elements like hover tooltips or drag-and-drop, which may not satisfy users accustomed to GUI debuggers.
The main README is brief, and users must refer to the wiki for important tasks, indicating potentially incomplete or scattered documentation for advanced features.