[Bug mi/9659] -break-list can produce non MI compliant output

["david.narvaez at computer dot org"<sourceware-bugzilla at sourceware dot org>]

http://sourceware.org/bugzilla/show_bug.cgi?id=9659

--- Comment #8 from David E. NarvÃez <david.narvaez at computer dot org> 2012-06-20 19:25:08 UTC ---
(In reply to comment #7)
> As you can see, it's unassigned since 2008... I don't even think that fixing
> the output is a good idea at this point: it may break all the front-ends, and
> will force their authors to support both variants for some time, adding
> complexity. And it's not like using the right formats will provide any more
> functionality/information - that's more a fix for the sake of fixing. Changing
> the documentation will "fix" it just as well, without breaking the existing
> code.

IIUC, that is to say we should ignore this bug because it has been ignored for
quite long. Extending this to every open bug in the bug tracker gives us an
easy way to drop the bug count to zero.

If fixing this will break frontends, well, the bugs themselves broke parsers in
those frontends and it doesn't look like anybody cares, so why would it matter
now? Plus, complex code for supporting two versions is as complex as the code
for supporting special cases of outputs, just that supporting a couple of
versions for some time is temporary.

That being said, I'm not a GDB developer so I can't take those decisions. What
I would like, though, is to see _any_ decision about these as I'm a frontend
developer and I need to know what will the final format of multiple breakpoints
be if  there is an open bug about it.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.