From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17592 invoked by alias); 29 May 2014 02:48:53 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 17575 invoked by uid 89); 29 May 2014 02:48:51 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 X-HELO: mail-pb0-f54.google.com Received: from mail-pb0-f54.google.com (HELO mail-pb0-f54.google.com) (209.85.160.54) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Thu, 29 May 2014 02:48:49 +0000 Received: by mail-pb0-f54.google.com with SMTP id jt11so12159310pbb.41 for ; Wed, 28 May 2014 19:48:47 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=yJXbbwOzb+Dx/j82hkZJQkOqklNd58D11mC0AXhws2I=; b=I5Pj6E98a7Ya3lHQZ7Y0DtfVGmvqLfDuKVc4l59AgjqEfq9ttUncTWriQNZtrQ8xCL 8M3/8UWvGjQZQ+urjI+8NiWVJ3Igi0ctkqBbIGp9zuROPgYZTxQYtyWTvIZKVidsdoEY O6Teg+DvsEIqxnMxn8b/oTGz9b9vxHFvGLABRngBITcYSvcbVBet6fYwojDcRjyOP5dv mLHQWdb03iojxWLc1cBsSuqIbC151tLfMZoNtrwFgxU8DcX0rlfL39TfifIXcMDoj0m5 qPQwx2dsSi8P5NvL4C3CYPgmTqW8WbVIH8ExoV3VKuqR/IJPrAYT6+Q91R3B62WWwB94 6WOQ== X-Gm-Message-State: ALoCoQnuGDbVtSiiua93vuz1+6upK1pMrlhwLwLBDq3C8M4Dm/DuRzBXYsTkqmN7XUOjiZiFvLEV X-Received: by 10.66.193.104 with SMTP id hn8mr4560615pac.99.1401331726998; Wed, 28 May 2014 19:48:46 -0700 (PDT) Received: from linux (ip68-9-64-242.ri.ri.cox.net. [68.9.64.242]) by mx.google.com with ESMTPSA id iz2sm30647750pbb.95.2014.05.28.19.48.45 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Wed, 28 May 2014 19:48:46 -0700 (PDT) Date: Thu, 29 May 2014 04:26:00 -0000 From: Bob Rossi To: Vladimir Prus Cc: gdb@sourceware.org Subject: Re: GDB/MI async output token field Message-ID: <20140529024922.GA3072@linux> References: <20140523011405.GA10166@linux> <538198B5.30208@cs.msu.su> <20140527155549.GA25063@linux> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140527155549.GA25063@linux> User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes X-SW-Source: 2014-05/txt/msg00080.txt.bz2 On Tue, May 27, 2014 at 11:55:49AM -0400, Bob Rossi wrote: > On Sun, May 25, 2014 at 11:16:05AM +0400, Vladimir Prus wrote: > > On 05/23/2014 05:14 AM, Bob Rossi wrote: > > >On this page, > > >https://sourceware.org/gdb/onlinedocs/gdb/GDB_002fMI-Output-Syntax.html#GDB_002fMI-Output-Syntax > > > > > >The documentation says, > > > Note that for all async output, while the token is allowed by the > > > grammar and may be output by future versions of gdb for select async > > > output messages, it is generally omitted. > > > > > > Frontends should treat all async output as reporting general changes in > > > the state of the target and there should be no need to associate async > > > output to any prior command. > > > > > >I searched through the GDB source code and can't find a single place > > >where this occurs. > > > > such clarification will be good. > > 2008-04-24 Vladimir Prus > > * gdb.texinfo (GDB/MI Output Syntax): Clarify that async > output does not necessary include any tokens. > > That looked a little suspicous. That is, perhaps there are cases were > the token is in the async output? > Perhaps I was unclear. I have a patch that removes the [token] syntax from the GDB manual regarding async output. I found your commit message that added a note that stated async output does not necessarily include tokens. The note made me think that at the time, you knew of at least one case where async output would include the token (or you would have removed the token syntax from the async output instead of saying that the token might not be included). Can you (or anyone) recall a case where GDB would output a token with an async record? I don't want to post a patch that removes the token syntax from the gdb manual if indeed someone will run into it in the wild. That makes the situation worse, not better. Thanks, Bob Rossi