From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30058 invoked by alias); 31 Jan 2019 15:54: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 30050 invoked by uid 89); 31 Jan 2019 15:54:20 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=1.3 required=5.0 tests=BAYES_50,KAM_NUMSUBJECT,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.2 spammy=H*UA:Roundcube, H*u:Roundcube, H*u:1.3.6, H*UA:1.3.6 X-HELO: smtp.polymtl.ca Received: from smtp.polymtl.ca (HELO smtp.polymtl.ca) (132.207.4.11) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 31 Jan 2019 15:54:19 +0000 Received: from simark.ca (simark.ca [158.69.221.121]) (authenticated bits=0) by smtp.polymtl.ca (8.14.7/8.14.7) with ESMTP id x0VFsCZh007646 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Thu, 31 Jan 2019 10:54:17 -0500 Received: by simark.ca (Postfix, from userid 112) id 3ADBC1E87B; Thu, 31 Jan 2019 10:54:12 -0500 (EST) Received: from simark.ca (localhost [127.0.0.1]) by simark.ca (Postfix) with ESMTP id 937F51E519; Thu, 31 Jan 2019 10:54:11 -0500 (EST) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Thu, 31 Jan 2019 15:54:00 -0000 From: Simon Marchi To: =?UTF-8?Q?=C3=96mer_Sinan_A=C4=9Facan?= Cc: gdb Subject: Re: Buildling gdb on Ubuntu 18.04 In-Reply-To: References: <35b21a4d59530644ce75e76fb8be8bbd@polymtl.ca> Message-ID: <090b2e06f4a14697a57b75e8b0556dfb@polymtl.ca> X-Sender: simon.marchi@polymtl.ca User-Agent: Roundcube Webmail/1.3.6 X-IsSubscribed: yes X-SW-Source: 2019-01/txt/msg00047.txt.bz2 On 2019-01-31 01:22, Ömer Sinan Ağacan wrote: >> Which bug are you referring to? Is it something know and documented >> in >> Bugzilla? > > I don't of if any of these are documented in Bugzilla, but > > - gdb sometimes prints more than one newline after a record. According > to > section 27.2.2 there should be only one newline. Oh, can you give a sequence of commands that triggers this? > - According to 27.2.2 a sequence of records result records should come > after > out-of-band record, but I sometimes get a sequence like > [out-of-bound, > result, out-of-bound]. I am not sure about the pedantic accuracy of the grammar for this, but I guess it works because the last out-of-band record can be considered as before the next result record, that has not yet arrived. The idea is that out-of-band records can happen pretty much at any time (and they are not necessarily related to the command you happen to have just issued previously). > - According to 27.2.2 a sequence of records should terminate with > "(gdb)\n" or > "(gdb)\r\n", but I get "(gdb) \n". We should check how old versions behaved, but I would guess that in this case it's the documentation that is wrong, and should include the space. Would you mind sending a patch for this? > - Most annoyingly, when I add a breakpoint to a location that > corresponds to > multiple locations in the source code (so it leads to adding more > than one > breakpoint), the mi syntax gdb prints looks like this > > =breakpoint-created,bkpt={...},{...},{...} > > which is not valid because a "result" should look like `x=y` so stuff > after > the first "result" (`bkpt={...}`) are not actually results. This last one is the one I aim to fix in https://sourceware.org/ml/gdb-patches/2019-01/msg00427.html Can you check if the proposed output makes sense to you? Simon