From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27304 invoked by alias); 4 Jun 2014 20:28:39 -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 27294 invoked by uid 89); 4 Jun 2014 20:28:38 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL autolearn=no version=3.3.2 X-HELO: mail.lvk.cs.msu.su Received: from lvk-gate.cs.msu.ru (HELO mail.lvk.cs.msu.su) (188.44.42.233) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Wed, 04 Jun 2014 20:28:36 +0000 Received: from mail.lvk.cs.msu.su (localhost.localdomain [127.0.0.1]) by mail.lvk.cs.msu.su (Postfix) with ESMTP id 6F525702134; Thu, 5 Jun 2014 00:28:26 +0400 (MSK) X-Spam-ASN: Received: from [192.168.0.103] (h86-62-88-129.ln.rinet.ru [86.62.88.129]) by mail.lvk.cs.msu.su (Postfix) with ESMTPSA id 55090702133; Thu, 5 Jun 2014 00:28:26 +0400 (MSK) Message-ID: <538F815E.9050702@cs.msu.su> Date: Wed, 04 Jun 2014 20:28:00 -0000 From: Vladimir Prus User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Bob Rossi CC: gdb@sourceware.org Subject: Re: GDB/MI async output token field References: <20140523011405.GA10166@linux> <538198B5.30208@cs.msu.su> <20140527155549.GA25063@linux> <20140529024922.GA3072@linux> <5386B6F1.1010708@cs.msu.su> <20140529190715.GA20321@linux> In-Reply-To: <20140529190715.GA20321@linux> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AV-Checked: ClamAV using ClamSMTP X-SW-Source: 2014-06/txt/msg00013.txt.bz2 On 05/29/2014 11:07 PM, Bob Rossi wrote: >> The ChangeLog entry is useless, as usual. Here are relevant emails: >> >> https://sourceware.org/ml/gdb/2008-03/msg00239.html >> https://sourceware.org/ml/gdb-patches/2008-04/msg00202.html >> >> The was single case where token was included in async output, and I removed >> that. I don't believe any new cases were added, and nobody was upset in >> all that time, so adjusting documentation to say that async output >> never includes any tokens seems reasonable to me. > > Thanks! That was very helpful. I've now reproduced this behavior. > > (gdb) > 111-exec-run > 111^running > (gdb) > 111*stopped,reason="breakpoint-hit",bkptno="1",thread-id="0",frame={addr="0x08048355",func="main",args=[],file="main.c",fullname="main.c",line="5"} > > The question now arises, is the intent of the documentation that ships > with GDB to accurately represent the current version of GDB or all > version up to and including the current version of GDB? > > The current version of GDB obviously does not use the token in the async > output, legacy versions do. > > Which should the documentation aim to match? I'd say the documentation should match the current version merely as a practical matter. Documenting every tweak will probably reduce readability too much. - Volodya