gdb-dashboard
voltron
Our great sponsors
| gdb-dashboard | voltron | |
|---|---|---|
| 19 | 5 | |
| 10,522 | 6,086 | |
| - | - | |
| 4.4 | 0.0 | |
| about 1 month ago | about 1 year ago | |
| Python | Python | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
gdb-dashboard
-
VSCode -> VIM, but how do I accomplish the other IDE tasks?
To debug, termdebug is built in to vim and supports a front end to gdb. In combination with gdb-dashboard this gives a reasonably good debugging experience
-
Are there any cpu emulators that could help me learn i386 assembly?
https://github.com/cyrus-and/gdb-dashboard, https://github.com/cyrus-and/gdb-dashboard/wiki
-
Debugging with GDB
I was using gdb-dashboard: https://github.com/cyrus-and/gdb-dashboard seems kind of like gef.
Try GDB Dashboard, it makes gdb much easier to use:
https://github.com/cyrus-and/gdb-dashboard
There's also Voltron which works with both gdb and lldb (amongst others):
I can't believe no one has mentioned `gdb-dashboard` [1] yet! I use it extensively. [2]
Beyond that, I have recently learned how to write custom pretty printers for GDB. This saves a lot of screen space. I should probably update [2] soon with those new techniques.
GDB is powerful, useful, and after getting my start in IDE debuggers, including Visual Studio, I struggle whenever I have to go back.
[1]: https://github.com/cyrus-and/gdb-dashboard
[2]: https://gavinhoward.com/2020/12/my-development-environment-a...
-
How do I "replicate" an IDE like the Keil uVision or the TI CCS using Visual Studio Code?
Debugging: Learn gdb. You can use it for assembly. You can use it for C on a MCU. You can use it for Go on a Linux system. It’s ubiquitous, versatile, and worth understanding. You can pretty-print the output with something like this to help you out at first. There are 2 things you need, however: on chip debugger and a debug probe (though you don’t need an expensive one). Effectively, you talk to GDB, GDB talks to the server exposed by OCD, OCD knows the debug probe protocol, and the debug probe can use the MCU debug peripheral via SWD or JTAG to get those details.
-
Non IDE debugger suggestions
gdb-dashboard: https://github.com/cyrus-and/gdb-dashboard Just a pretty wrapper for gdb, so it’s as stable as gdb itself. Pretty good if you like to stay in the terminal. You can run python scripts from it since you’re actually in gdb
-
How to access Cortex-M's General-purpose registers
I would even suggest use of System View Description – I use gdb-dashboard + gdb-dashboard-svdregisters. There are alternatives, of course.
-
GDB TUI mode
There are a couple of wrappers that try to enhance it like GDB dashboard and GEF.
voltron
-
Debugging a Mixed Python and C Language Stack
https://github.com/snare/voltron
> * https://developers.redhat.com/blog/2017/11/10/gdb-python-api... describes the GDB Python API.*
> https://pythonextensionpatterns.readthedocs.io/en/latest/deb... may be helpful [for writing-a-c-function-to-call-any-python-unit-test]
> The GDB Python API docs: https://sourceware.org/gdb/onlinedocs/gdb/Python-API.html
> The devguide gdb page may be the place to list IDEs with support for mixed-mode debugging of Python and C/C++/Cython specifically with gdb?
-
Debugging with GDB
In a past life I used Voltron[0] with lldb. Depending on your use case, it might be enough? Watching what value lives in what register works at least (or at least worked last time I used it). It's designed around having things in separate terminals, so you'll need tmux/screen/tiling window manager to get a similar view to gef.
Try GDB Dashboard, it makes gdb much easier to use:
https://github.com/cyrus-and/gdb-dashboard
There's also Voltron which works with both gdb and lldb (amongst others):
- Announcement about Maintenance of GDBFrontend
What are some alternatives?
gef - GEF (GDB Enhanced Features) - a modern experience for GDB with advanced debugging capabilities for exploit devs & reverse engineers on Linux
lldb-mi - LLDB's machine interface driver
pdb-tutorial - A simple tutorial about effectively using pdb
nvim-gdb - Neovim thin wrapper for GDB, LLDB, PDB/PDB++ and BashDB
pwndbg - Exploit Development and Reverse Engineering with GDB Made Easy
gdb-frontend - ☕ GDBFrontend is an easy, flexible and extensible gui debugger. Try it on https://debugme.dev
syntax-highlighting - A fork of Tiago Barroso's Syntax Highlighting add-on with support for Anki 2.1
gdb-dashboard-svdregisters - Tool and module for adding any register to gdbinit from svd-file
clasp - clasp Common Lisp environment