gdb-dashboard icon indicating copy to clipboard operation
gdb-dashboard copied to clipboard

Modular visual interface for GDB in Python

Results 19 gdb-dashboard issues
Sort by recently updated
recently updated
newest added

As briefly discussed in #59 and #174 the unsteadiness of the output due to dynamically resized panes and the unavoidable output of gdb is a PITA when single-stepping and staring...

improvement

Would it be possible to change the color of watch expression lines that have changed since the last update?

feature request

On gdb shell, **print ** must wait for user to press enter for more and q for quit and c for continue to print till end. But not happening ....

I missed a convenient way to constantly watch a memory region with the format options of GDB's "x" command (e. g. watching not only single bytes). This is a rewrite...

In gdb + dashboard, when I stepped over the code, sometimes, the dashboard screen would be flickering. The reason seems to be the random appearance/disappearance of original gdb one-line source...

OS: Debian 12 I'm trying to use `gdb-dashboard` for the first time. I have installed `Pygments` as mentioned in the README. In the `Output/messages` module, syntax highlighting looks good: ![image](https://github.com/cyrus-and/gdb-dashboard/assets/31297905/6e7818c7-981a-4414-8297-7ec308248d08)...

Dashboard used to not display breakpoint cause my breakpint were hardware one's. This add a string to the Breakpoints.NAMES dict so HW breakpoints would be displayed correctly

The dashboard has a few issues when gdb connects to the qemu gdb stub. One of which is the parsing function for breakpoints, which can't handle hardware breakpoints. ``` Num...

``` wget -P ~ https://github.com/cyrus-and/gdb-dashboard/raw/master/.gdbinit gdb -ex r --args python code/armstrong.py ``` armstrong.py: ``` [...] while temp > 0: digit = temp % 10 sum += digit ** order temp...

not a bug