Re: bug in mi when setting breakpoint

Nick Roberts
2008-01-15T03:37:49Z

> Unfortunately CLI also uses sub-prompts for several other commands: queries
> e.g pending breakpoints, exiting after exevution has started; the "commands"
> command. I don't think that they fit well with the MI paradigm: MI expects
> MI output. With queries, GDB takes affirmative action, e.g., creates
> pending breakpoints regardless of the value of "show breakpoint pending" and
> exits regardless of the value of "show confirm".
>
> Perhaps, for now, GDB could do something similar, i.e., set all the
> breakpoints in the breakpoint menu.

I see now that this is what Apple do:

if (i1 > 0)
{
int accept_all;
if (ui_out_is_mi_like_p (uiout))
accept_all = 1;
else
accept_all = 0;

/* There is more than one field with that name
(overloaded). Ask the user which one to use. */
return decode_line_2 (sym_arr, i1, i1, funfirstline, accept_all,
canonical);
}

How about doing something similar in FSF GDB?