This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Incorrect breakpoint diagnostics in MI


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.



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]