From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27228 invoked by alias); 4 May 2008 16:49:12 -0000 Received: (qmail 27218 invoked by uid 22791); 4 May 2008 16:49:12 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 04 May 2008 16:48:55 +0000 Received: (qmail 18772 invoked from network); 4 May 2008 16:48:53 -0000 Received: from unknown (HELO localhost) (vladimir@127.0.0.2) by mail.codesourcery.com with ESMTPA; 4 May 2008 16:48:53 -0000 From: Vladimir Prus To: Daniel Jacobowitz Subject: Re: Fix MI/async testsuite Date: Sun, 04 May 2008 17:22:00 -0000 User-Agent: KMail/1.9.6 (enterprise 0.20070907.709405) Cc: gdb-patches@sourceware.org References: <200805041618.14962.vladimir@codesourcery.com> <20080504163321.GA17507@caradoc.them.org> In-Reply-To: <20080504163321.GA17507@caradoc.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200805042048.21287.vladimir@codesourcery.com> 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: 2008-05/txt/msg00175.txt.bz2 On Sunday 04 May 2008 20:33:21 Daniel Jacobowitz wrote: > On Sun, May 04, 2008 at 04:18:14PM +0400, Vladimir Prus wrote: > > > > My previous patches to add =thread-created have broken MI testsuite > > in async mode, since in async mode, the order of output is somewhat > > different and the output for -exec-run is: > > > > ^running > > =thread-created > > (gdb) > > > > with =thread-creating going before prompt, while in sync mode > > (gdb) follows ^running immediately. > > Is this syntax only recently allowed and not yet documented? I built > the current info docs from CVS and the grammar does not allow for > RESULT-RECORD OUT-OF-BAND-RECORD (gdb) NL. Guess this is because I did not update the grammar per earliner discussion. We should have RESULT-RECORD, OUT-OF-BAND-RECORD and PROMPT be independent, and allowed to appear in any order. > =thread-created after *running makes lots of sense. =thread-created > after ^running is a little weird to me. If ^running is the response > to a command it ought to be followed by a prompt. Per current grammar, yes. In principle, no -- prompt indicates that gdb is ready to accept further input, and should be printed, naturally, when gdb is ready to accept more input -- which is not necessary right after printing "^running". - Volodya