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 Type Disp Enb Address What
1 hw breakpoint keep y 0x010055d0 in main() at main.cc:24
Traceback (most recent call last):
File "<string>", line 550, in render
File "<string>", line 2293, in lines
KeyError: 2
Why did you decide to parse the output instead of using gdb.breakpoints()?
The provided issue (https://sourceware.org/bugzilla/show_bug.cgi?id=18385) has been fixed since 13.1.
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.
Why did you decide to parse the output instead of using
gdb.breakpoints()?The provided issue (https://sourceware.org/bugzilla/show_bug.cgi?id=18385) has been fixed since 13.1.