[Bug mi/9659] -break-list can produce non MI compliant output
palves at redhat dot com
sourceware-bugzilla@sourceware.org
Sat Sep 29 18:57:00 GMT 2018
https://sourceware.org/bugzilla/show_bug.cgi?id=9659
Pedro Alves <palves at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |palves at redhat dot com
--- Comment #18 from Pedro Alves <palves at redhat dot com> ---
I wasn't involved in the irc discussion, but I've discussed this with Simon
before. Adding my 2c.
IMO, we should go the -break-list-2 route.
Tying command fixes to MI versions (like the v4 idea) is an inferior solution
IMO, because then you can't e.g., backport individual command fixes. It's an
either all-or-nothing solution. To get a fix present in v6, you need all of
v3, v4, v5.
I'd think a jump of MI version would only be justified when we want to change
something fundamental that would break compatibility across manhy commands and
events, like switching to json, or changing how lists/tuples/etc. are
represented, or something like that.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Gdb-prs
mailing list