Re: [PATCH] Re: bug in mi when setting breakpoint

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

Nick Roberts wrote:

>  > This is different to what I've proposed -- namely reporting "there are
>  > several overloaded functions" and then allowing the frontend to select
>  > a specific one.
> 
> I must have missed that.  Can you please point to a reference?

I can't immediately find that; the point was that -break-insert would
list all possible function on which breakpoint can be set, without setting
any. Then frontend will then specifically set breakpoints on the function
it wants.

> 
>  >               The solution you propose does not give a frontend a way
>  >               to
>  > control which overloaded function to set breakpoint on, which seems
>  > like an important limitation for me.
> 
> After selecting all breakpoints GDB prints:
> 
>   warning: Multiple breakpoints were set.
>   Use the "delete" command to delete unwanted breakpoints.
> 
> I can see it may be an inconvenience but not how it can be a limitation.
> IMHO, it seems preferable to generating prompts that are not compatible
> with rules for MI output.

To clarify -- are you suggesting what we should first create breakpoints
for all overloaded function, and then remove those we don't need, in MI?

- Volodya