From: Doug Evans <dje@google.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
gdb-patches@sourceware.org, Marek Polacek <mpolacek@redhat.com>
Subject: Re: [patch] testsuite: MI: racy results in async mode (PR testsuite/12649)
Date: Tue, 01 Nov 2011 22:46:00 -0000 [thread overview]
Message-ID: <CADPb22S2aOX9vkzWAx-95QYQGe0EHY-rVgDE1DRT96yi=jJ5zQ@mail.gmail.com> (raw)
In-Reply-To: <m37h3j3gbq.fsf@fleche.redhat.com>
On Tue, Nov 1, 2011 at 10:25 AM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Doug" == Doug Evans <dje@google.com> writes:
>
> Jan> The fix is ugly but it cannot be done better before there is a generic MI
> Jan> client parser deployed for the testsuite.
>
> Doug> What does "generic MI client parser" mean in this context?
>
> Right now MI parsing in the test suite is done in an ad hoc manner.
> E.g., see mi_create_breakpoint.
>
> It would be more robust if we had an MI parser in Tcl so that we could
> parse the output as clients do.
>
> As far as I know nobody is planning to actually do this though.
Not that I'm planning to do this :-), but would an MI parser written
in C that could be exported to Tcl, Python, etc. be of sufficient use
beyond the testsuite to entice someone to write one? One can load C
modules into Tcl, and I'm guessing(!) the glue to make it usable to
the testsuite would be minimal.
next prev parent reply other threads:[~2011-11-01 22:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 10:16 Jan Kratochvil
2011-10-27 16:49 ` Tom Tromey
2011-10-28 8:51 ` [commit] " Jan Kratochvil
2011-10-29 10:36 ` [patch] testsuite: MI: racy results in async mode #2 Jan Kratochvil
2011-10-29 12:10 ` Marek Polacek
2011-10-29 12:15 ` Marek Polacek
2011-10-29 15:09 ` Jan Kratochvil
2011-10-29 16:01 ` Marek Polacek
2011-11-01 16:20 ` Tom Tromey
2011-11-01 20:01 ` [commit] " Jan Kratochvil
2011-11-01 16:26 ` Marek Polacek
2011-11-01 15:40 ` [patch] testsuite: MI: racy results in async mode (PR testsuite/12649) Doug Evans
2011-11-01 16:26 ` Jan Kratochvil
2011-11-01 18:55 ` Tom Tromey
2011-11-01 22:46 ` Doug Evans [this message]
2011-11-02 17:31 ` Tom Tromey
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='CADPb22S2aOX9vkzWAx-95QYQGe0EHY-rVgDE1DRT96yi=jJ5zQ@mail.gmail.com' \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=mpolacek@redhat.com \
--cc=tromey@redhat.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