This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug mi/9659] -break-list can produce non MI compliant output
- From: "dimitar.zhekov at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 21 Jun 2012 19:06:51 +0000
- Subject: [Bug mi/9659] -break-list can produce non MI compliant output
- Auto-submitted: auto-generated
- References: <bug-9659-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=9659
--- Comment #9 from Dimitar Zhekov <dimitar.zhekov at gmail dot com> 2012-06-21 19:06:51 UTC ---
Your point is valid, of course. But once again: the right formats will not
provide any more or better MI functionality.
I am a front-end developer as well. Discarding the difference between list and
tuple, and allowing a mix of named and unnamed arguments, produced a bit
simpler parser for me. But I was only checking the presence or lack of names to
make sure that the output is MI-compliant anyway. Your approach may be
different.
However, "bkpt=" for locations will affect me. :( When a breakpoint lacks
"type=...", my break parsing tries the tuple name next, as in "done,wpt={...}".
So I, too, would like to know what the final MULTIPLE format will be.
--
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.