From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28341 invoked by alias); 1 Nov 2011 18:55:52 -0000 Received: (qmail 28312 invoked by uid 22791); 1 Nov 2011 18:55:51 -0000 X-SWARE-Spam-Status: No, hits=-7.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 01 Nov 2011 18:55:36 +0000 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id pA1ItJqU008354 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 1 Nov 2011 14:55:35 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id pA1HPlKh000702; Tue, 1 Nov 2011 13:25:47 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id pA1HPk71028079; Tue, 1 Nov 2011 13:25:46 -0400 From: Tom Tromey To: Doug Evans Cc: Jan Kratochvil , gdb-patches@sourceware.org, Marek Polacek Subject: Re: [patch] testsuite: MI: racy results in async mode (PR testsuite/12649) References: <20111027101544.GA5288@host1.jankratochvil.net> Date: Tue, 01 Nov 2011 18:55:00 -0000 In-Reply-To: (Doug Evans's message of "Tue, 1 Nov 2011 08:40:02 -0700") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.90 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-11/txt/msg00027.txt.bz2 >>>>> "Doug" == Doug Evans 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. Tom