Debugger (gdb) ommits important info if stepping fails due to bad breakpoint
If a bad breakpoint (e.g. address-breakpoint at impossible address like $000111) exists, the debugger can not continue stepping, as it can not set the breakpoint.
It displays an error, but it shows no hint towards the cause.
Even the more button will only show "Command aborted." It does not include any of the warnings. (see below).
This also can happen during startup. (as reported in #39392 (closed))
<-exec-next> ^running *running,thread-id="all" (gdb) &"Warning:\n" &"Cannot insert breakpoint 8.\n" &"Cannot access memory at address 0x111\n" &"\n" ^error,msg="Command aborted." (gdb)