From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 47513 invoked by alias); 30 Jan 2019 20:01:28 -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 47431 invoked by uid 89); 30 Jan 2019 20:01:28 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-0.0 required=5.0 tests=BAYES_05,KAM_NUMSUBJECT,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.2 spammy=docker, H*f:sk:3C1-4GD, H*f:sk:zPk_p53, H*f:CAMQQO3 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; Wed, 30 Jan 2019 20:01:27 +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 x0UK1KQt019491 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Wed, 30 Jan 2019 15:01:25 -0500 Received: by simark.ca (Postfix, from userid 112) id B00141E882; Wed, 30 Jan 2019 15:01:20 -0500 (EST) Received: from simark.ca (localhost [127.0.0.1]) by simark.ca (Postfix) with ESMTP id E80E51E472; Wed, 30 Jan 2019 15:01:18 -0500 (EST) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Wed, 30 Jan 2019 20:01: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: X-Sender: simon.marchi@polymtl.ca User-Agent: Roundcube Webmail/1.3.6 X-IsSubscribed: yes X-SW-Source: 2019-01/txt/msg00044.txt.bz2 On 2019-01-30 14:45, Ömer Sinan Ağacan 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