From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 129278 invoked by alias); 24 Apr 2019 19:28:51 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 129270 invoked by uid 89); 24 Apr 2019 19:28:50 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-7.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS autolearn=ham version=3.3.1 spammy=HX-Languages-Length:979, Zaretskii, eliz@gnu.org, elizgnuorg X-HELO: gateway21.websitewelcome.com Received: from gateway21.websitewelcome.com (HELO gateway21.websitewelcome.com) (192.185.45.212) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 24 Apr 2019 19:28:49 +0000 Received: from cm10.websitewelcome.com (cm10.websitewelcome.com [100.42.49.4]) by gateway21.websitewelcome.com (Postfix) with ESMTP id 1C98040117BDC for ; Wed, 24 Apr 2019 14:28:48 -0500 (CDT) Received: from box5379.bluehost.com ([162.241.216.53]) by cmsmtp with SMTP id JNZYhaGNz2PzOJNZYh60WZ; Wed, 24 Apr 2019 14:28:48 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tromey.com; s=default; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date: References:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=hDHy3VWfE8ze/RDAXjgtHAqDk5vtpm4A98HhgmFTnHE=; b=VDItU4rXB55pG4EM/mhu5+tHph uq9ADXl+zGxCYbiFUnGwzBw/1gm8hA4f8b0uWqshkHKHJ2l+ljBe8s0moOf8yOKU/mvSB9wi4K9V0 iDR53T5rFA6DrcH5JlJkWWIiB; Received: from 97-122-168-123.hlrn.qwest.net ([97.122.168.123]:54594 helo=murgatroyd) by box5379.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from ) id 1hJNZX-003eII-SK; Wed, 24 Apr 2019 14:28:47 -0500 From: Tom Tromey To: Eli Zaretskii Cc: LRN , gdb-patches@sourceware.org Subject: Re: Warning when using separate debug info file References: <83y348edoi.fsf@gnu.org> <20439f48-c0ff-e4b2-5cfc-6bb4b594d88c@gmail.com> <83h8aveape.fsf@gnu.org> <66d48dfd-23ac-7e05-3ad8-4e65b0c1c7f9@gmail.com> <834l6vdv4y.fsf@gnu.org> Date: Wed, 24 Apr 2019 19:28:00 -0000 In-Reply-To: <834l6vdv4y.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 18 Apr 2019 21:29:49 +0300") Message-ID: <87k1fjfbio.fsf@tromey.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2019-04/txt/msg00493.txt.bz2 >>>>> "Eli" == Eli Zaretskii writes: >> The hypothesis is...actually, no, i have no idea. I mean, it's obvious that gdb >> expects to find that section in a separate debug file for some reason. Probably >> because separate debug files are just PE binaries, and the code that reads them >> is heavily re-used. Or maybe gdb supports recursive debuglinks? Eli> But then why doesn't this happen on GNU/Linux? Those platforms moved away from the .gnu_debuglink approach to use build-id instead. See (info "(gdb) Separate Debug Files") I don't really recall how .gnu_debuglink works, but I am somewhat surprised to hear it should be in the separate debug file. My understanding of it was that it recorded a CRC and the verification happened by computing the CRC of the separate debug file (this is expensive, which is why build-id is superior...). So I suppose this is just a bug but the cause remains unknown. Tom