Incorrect breakpoint diagnostics in MI
Konstantin Karganov
kostik@ispras.ru
Thu Jul 14 15:15:00 GMT 2005
Hello.
Playing with MI breakpoint commands I found the following thing:
Only "-break-after" and "-break-condition" correctly report the error if
the breakpoint doesn't exist. While other commands report "^done".
(gdb)
-break-after 123 123
&"No breakpoint number 123.\n"
^error,msg="No breakpoint number 123."
(gdb)
-break-enable 123
~"No breakpoint number 123.\n"
^done
(gdb)
-break-disable 123
~"No breakpoint number 123.\n"
^done
(gdb)
-break-delete 123
~"No breakpoint number 123.\n"
^done
The diagnostics goes to console output, that is possibly not visible to FE
user and the result itself is "ok".
Is it a bug?
Best reagards,
Konstantin.
More information about the Gdb
mailing list