From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 37105 invoked by alias); 31 Jan 2019 06:23:38 -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 37097 invoked by uid 89); 31 Jan 2019 06:23:38 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: =?ISO-8859-1?Q?No, score=1.3 required=5.0 tests=BAYES_50,FREEMAIL_FROM,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 spammy=D*ca, oca, docker, yazd=c4=b1?= X-HELO: mail-pf1-f180.google.com Received: from mail-pf1-f180.google.com (HELO mail-pf1-f180.google.com) (209.85.210.180) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 31 Jan 2019 06:23:36 +0000 Received: by mail-pf1-f180.google.com with SMTP id u6so1012747pfh.11 for ; Wed, 30 Jan 2019 22:23:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=vnyaA7tYv3pJ1rrd5hEBOUZtyvyF4JX6eZ2zAwhcWeM=; b=Xr00/O9F8V4Ks/mq+VsrVw3kKB5fs4Oc/Ifcbvu1sZoFZ39uDjVZVgPqocH4viyMHS 0zfJ7fhQHep1IlRaU+q/l9in9GFdrPdWo5TXRX6Zhy+OoGzFW3b3+TRZumd4Szq1ZkBg 9QhH7Fi9zx6HAKHMHbaZMF5NKkzP3d0+z6oWDDQ8hrSzkfuyMEz88dQ9uQl5TEoEYhri JjJgk/ycI222H7ShUUYUX+vPG4JxXeXClSqBx/h5Iiu2ae60y6SZJMLNGm0+W11FFJYU 259nt91UHc2yX40U1GAz/YsCTqsbcSvu3RRws+9ScJZejotzzn2EBONVNrFPtqIVNSqX rkpw== MIME-Version: 1.0 References: <35b21a4d59530644ce75e76fb8be8bbd@polymtl.ca> In-Reply-To: From: =?UTF-8?Q?=C3=96mer_Sinan_A=C4=9Facan?= Date: Thu, 31 Jan 2019 06:23:00 -0000 Message-ID: Subject: Re: Buildling gdb on Ubuntu 18.04 To: Simon Marchi Cc: gdb Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-SW-Source: 2019-01/txt/msg00046.txt.bz2 > 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. - 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]. - According to 27.2.2 a sequence of records should terminate with "(gdb)\n"= or "(gdb)\r\n", but I get "(gdb) \n". - 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 =3Dbreakpoint-created,bkpt=3D{...},{...},{...} which is not valid because a "result" should look like `x=3Dy` so stuff a= fter the first "result" (`bkpt=3D{...}`) are not actually results. =C3=96mer Simon Marchi , 30 Oca 2019 =C3=87ar, 23:01 tarihinde =C5=9Funu yazd=C4=B1: > > On 2019-01-30 14:45, =C3=96mer Sinan A=C4=9Facan wrote: > > Interesting, I was also able to build in a docker container and it > > works when I > > copy the executable to the host system, so my problem is kind of > > solved. I'm > > still wondering what's wrong with my system though ... > > > > (Too bad the bug exists in the development version too so I have to > > deal with it > > in my application...) > > Sorry for not being able to help you for your build issue, it looks like > a one off weird thing with your setup (with enough digging one would > probably find it). > > Which bug are you referring to? Is it something know and documented in > Bugzilla? > > Simon