This is the mail archive of the
mailing list for the GDB project.
Re: [patch] testsuite: MI: racy results in async mode (PR testsuite/12649)
- From: Doug Evans <dje at google dot com>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: Jan Kratochvil <jan dot kratochvil at redhat dot com>, gdb-patches at sourceware dot org, Marek Polacek <mpolacek at redhat dot com>
- Date: Tue, 1 Nov 2011 15:46:16 -0700
- Subject: Re: [patch] testsuite: MI: racy results in async mode (PR testsuite/12649)
- References: <20111027101544.GA5288@host1.jankratochvil.net> <CADPb22SeaD5Tv9gqnvc45Riv3ZMW=9bAW2F-S164QNBLEV=C3Q@mail.gmail.com> <email@example.com>
On Tue, Nov 1, 2011 at 10:25 AM, Tom Tromey <firstname.lastname@example.org> wrote:
>>>>>> "Doug" == Doug Evans <email@example.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.