From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16724 invoked by alias); 27 May 2014 15:55:21 -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 16712 invoked by uid 89); 27 May 2014 15:55:20 -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-f42.google.com Received: from mail-pb0-f42.google.com (HELO mail-pb0-f42.google.com) (209.85.160.42) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Tue, 27 May 2014 15:55:19 +0000 Received: by mail-pb0-f42.google.com with SMTP id md12so9496724pbc.15 for ; Tue, 27 May 2014 08:55:17 -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=HB2Rkk4OeAXx6+5ao++inPUMqIDnZteGDA0vx/eSJZY=; b=muBPxCZQcnvzoBjeEbu60wYPDUG6QPCUMY8qy4MuwC1aq7C5nWf4PEnLX1Ur8Jbhv8 S703ceD1VDKegQk8bNwgCG0wbuRYNsHOsn+uRLxkosz/TKmMpXRRTLSpSKYal6IlpxuP OXqvm4eX2V5Y4eF5dxB8fRLoCTvgJbvwMIyirZTfYEhSci2nlvxVpGbhximz9qUusC5Q 5GPhu7aJmDUqc+eXOBNPSF3KIqBy2LngTF4gQQk5q2NICEEnncaraHmoFU0Nxk2XtiHi +lcLVl++9M2uoKc/N3aITkAEYBpfm1XM5JS4t5xWWvlUEzOuE6C1TSolbO5RM/l1hCtJ DN2g== X-Gm-Message-State: ALoCoQl/n1bO5PbJjS1XwubLRmGsSg36wSwFfbrNeZirHFW9p9PpHSRhRQ7quw+WTyFEmm55thX2 X-Received: by 10.66.232.68 with SMTP id tm4mr37288625pac.114.1401206117853; Tue, 27 May 2014 08:55:17 -0700 (PDT) Received: from linux (ip68-9-64-242.ri.ri.cox.net. [68.9.64.242]) by mx.google.com with ESMTPSA id dd5sm23940553pbc.85.2014.05.27.08.55.15 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Tue, 27 May 2014 08:55:17 -0700 (PDT) Date: Wed, 28 May 2014 07:59:00 -0000 From: Bob Rossi To: Vladimir Prus Cc: gdb@sourceware.org Subject: Re: GDB/MI async output token field Message-ID: <20140527155549.GA25063@linux> References: <20140523011405.GA10166@linux> <538198B5.30208@cs.msu.su> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <538198B5.30208@cs.msu.su> User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes X-SW-Source: 2014-05/txt/msg00076.txt.bz2 On Sun, May 25, 2014 at 11:16:05AM +0400, Vladimir Prus wrote: > On 05/23/2014 05:14 AM, Bob Rossi wrote: > >Hi, > > > >I'm slowly working through the GDB/MI output command functionality. > > > >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. > > > >Does anyone know how to make a token appear in the async record? > >Did older versions do it? > > > >If GDB is not using this feature, I propose we remove this information > >from the manual until we actually need the functionality. > > Bob, > > such clarification will be good. Hi, I've got a patch to change the documentation to remove the tokens from the async output records. I saw this in the ChangeLog, 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? Are you aware of any such cases? It doesn't look like the current version of GDB emits this information, but perhaps older versions do? Before I submit my patch I'd like to have this issue resolved. It doesn't make sense to submit my current patch if old versions of GDB can produce this content. Thanks, Bob Rossi