Re: [BUG:MI] -break-list doesn't list multiple breakpoints

[Vladimir Prus <ghost@cs.msu.su>]

Nick Roberts wrote:

> 
> I have previously mentioned this in
> 
>        http://sourceware.org/ml/gdb-patches/2007-11/msg00276.html
> 
> breakpoint.c currently has:

Yes, we had this conversation before...
 
>       if (b->loc
> && (b->loc->next || !b->loc->enabled))
> && !ui_out_is_mi_like_p (uiout))
> {
> struct bp_location *loc;
> int n = 1;
> for (loc = b->loc; loc; loc = loc->next, ++n)
> print_one_breakpoint_location (b, loc, n, last_addr);
> }
> 
> where presumably the !ui_out_is_mi_like_p (uiout) bit is there because the
> testsuite failed without it, i.e., so that -break-insert only reports one
> breakpoint (the CLI command "break" doesn't use
> print_one_breakpoint_location).

No, merely because I had no time to design MI interface.

> On a more general note, in Emacs, I just just use "info break" after every
> user
> command and will probably just use "-break-list" in the future.  I won't
> use the output of -break-insert, although some front end might be clever
> enough to do this and that presumably was the intention when the command
> was written. In that case it might be necessary to include all the
> locations in a multiple breakpoint in the output.
> 
> Support for CLI in frontends can only be dropped after MI is fully
> functional, it makes no sense to to do it before.

I am not sure about your point. Clearly, MI needs some work still,
but it's true for several years already.

- Volodya