This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


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

perret at mailbox dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |perret at mailbox dot org

--- Comment #19 from perret at mailbox dot org ---
As a frontend implementor I'm in favor of a new mi version. The frontend I'm
working on (https://github.com/occivink/kakoune-gdb) uses new-ui such that the
user can control gdb from either the IDE or the gdb cli. Introducing a new
-break-insert-2 wouldn't work in my case because I receive both synchronous and
asynchronous outputs, and this mechanism does not control the async format.

My preferred solution would be an mi4-experimental with no stability guarantee
where breaking changes are progressively accumulated, to be renamed to mi4
after some time. I also think this should be used to make all possible outputs
compliant with the grammar. The format should be simple to parse, but instead
each frontend implementor has to waste time discovering this bug and
introducing hacks to work around it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]