From: Tom Tromey <tromey@redhat.com>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
gdb-patches@sources.redhat.com,
Dodji Seketeli <dseketel@redhat.com>
Subject: Re: [patch] MI: breakpoint "script" is a LIST
Date: Thu, 13 Nov 2008 21:35:00 -0000 [thread overview]
Message-ID: <m31vxfa96u.fsf@fleche.redhat.com> (raw)
In-Reply-To: <200811131834.26373.vladimir@codesourcery.com> (Vladimir Prus's message of "Thu\, 13 Nov 2008 18\:34\:26 +0300")
>>>>> "Vladimir" == Vladimir Prus <vladimir@codesourcery.com> writes:
Jan> The current code does not comply to any generic MI parser as it
Jan> violates the MI grammar
Jan> http://sourceware.org/gdb/current/onlinedocs/gdb_26.html#SEC264 ,
Jan> as pointed out by Dodji.
Jan> It may be compliant only to some hacky buggy parsers written
Jan> specifically for each MI command.
Vladimir> That's interesting statement -- are you saying all MI
Vladimir> frontends out there have "hacky buggy parsers"?
I think he is saying that the MI output of gdb, in this case, does not
conform to the MI grammar as given in the manual. So, if an
implementer tries to write an MI parser relying strictly on the
grammar, it will not work in this case. From one point of view this
means having a hacky parser...
Vladimir> This breakage is relatively new ;-)
Vladimir> Date: Sat May 12 04:08:24 2001 +0000
Yuck. I guess options for fixing this are pretty limited.
How about documenting, in the "GDB/MI Output Syntax" node, that
sometimes lists are formatted like tuples? That may, at least,
prevent future MI implementers from having to rediscover this problem
on their own.
Tom
next prev parent reply other threads:[~2008-11-13 16:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 15:11 Jan Kratochvil
2008-11-13 15:35 ` Vladimir Prus
2008-11-13 15:39 ` Jan Kratochvil
2008-11-13 20:21 ` Vladimir Prus
2008-11-13 21:35 ` Tom Tromey [this message]
2008-11-13 21:55 ` Marc Khouzam
2008-11-13 21:59 ` Jan Kratochvil
2008-11-16 8:23 ` André Pönitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m31vxfa96u.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dseketel@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jan.kratochvil@redhat.com \
--cc=vladimir@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox