[RFC] Fix the MI result of -break-insert with multiple locations

[André Pönitz]

On Tue, Jan 29, 2013 at 08:42:39PM +0000, Marc Khouzam wrote:
> > This seems more like an additional burden for frontends which cannot
> > rely on a specific gdb version being installed as they have to keep
> > code to parse both results, for years.
> 
> Although that is a good point, keeping it forces frontends to deal
> with that case.

I don't think it needs special "dealing" as I assume that existing 
frontend parsers are just robust enough to accept such cases.

Changing the nesting of structures on the other hand usually
needs adjustment to the interpretation of the parsed structure.

I am not scared of adding yet another ten lines to find out which
kind of output the user's choice of GDB produces and to handle
both versions, I just find it not particular convenient. 

Andre'

PS: This point remains:

> > An alternative approach would be to just make the
> > documentation match the actual output. This is not
> > unprecedented.

PPS: In theory "-list-features" could be used to announce output
changes to avoid the "guessing" phase.