From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca (simark.ca [158.69.221.121]) by sourceware.org (Postfix) with ESMTPS id DAD52383F868 for ; Wed, 27 May 2020 21:55:15 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org DAD52383F868 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=simark.ca Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=simark@simark.ca Received: from [172.16.0.95] (192-222-181-218.qc.cable.ebox.net [192.222.181.218]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id 74C071E072; Wed, 27 May 2020 17:55:15 -0400 (EDT) Subject: Re: [PATCH v2 28/42] Remove dwarf2_per_cu_data::objfile () To: Tom de Vries , Simon Marchi , gdb-patches@sourceware.org References: <20200512210913.5593-1-simon.marchi@efficios.com> <20200512211250.6230-29-simon.marchi@efficios.com> <04473d43-9719-436b-648a-bdc8e5f55751@suse.de> <354bbf9d-6bca-deaa-c64b-714c8d6b477d@suse.de> From: Simon Marchi Message-ID: Date: Wed, 27 May 2020 17:55:14 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <354bbf9d-6bca-deaa-c64b-714c8d6b477d@suse.de> Content-Type: text/plain; charset=utf-8 Content-Language: tl Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-8.0 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, SPF_HELO_PASS, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 May 2020 21:55:19 -0000 On 2020-05-27 5:08 p.m., Tom de Vries wrote: >> I don't see this failure. Is it with a particular board file? Or maybe >> gcc-version specific? >> > > No, this is with native, and reproduced with gcc 7.5.0, gcc 4.8.5, gcc > 10.1.1 and clang 5.0.2. > >> It looks related to what we have discussed here: >> >> https://sourceware.org/pipermail/gdb-patches/2020-May/168906.html >> >> I think the fix would be to temporarily override this->per_objfile to be >> caller_per_objfile (with a scoped_restore). But I'd like to be able to >> reproduce it to understand what's happening. > > I think maybe installing debug info for glibc and building with > --with-separate-debug-dir=/usr/lib/debug may do the trick. > > Thanks, > - Tom > I do have debug info for glibc and it is found: (gdb) info shared >From To Syms Read Shared Object Library 0x00007ffff7dd7ac0 0x00007ffff7df5790 Yes /lib64/ld-linux-x86-64.so.2 0x00007ffff7bd3da0 0x00007ffff7bd498e Yes /lib/x86_64-linux-gnu/libdl.so.2 0x00007ffff78288b0 0x00007ffff797bb04 Yes /lib/x86_64-linux-gnu/libc.so.6 I tested with these two gccs: $ gcc --version gcc (Ubuntu 5.5.0-12ubuntu1~16.04) 5.5.0 20171010 $ gcc-9 --version gcc-9 (Ubuntu 9.3.0-10ubuntu2~16.04) 9.3.0 I will give a shot at building GDB in an opensuse container [1], we'll see. Simon [1] https://hub.docker.com/r/opensuse/leap