From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 75954 invoked by alias); 1 Mar 2018 21:05:19 -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 75288 invoked by uid 89); 1 Mar 2018 21:05:18 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-6.9 required=5.0 tests=BAYES_00,GIT_PATCH_1,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=yyy, xxx X-HELO: mx1.redhat.com Received: from mx3-rdu2.redhat.com (HELO mx1.redhat.com) (66.187.233.73) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 01 Mar 2018 21:05:17 +0000 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 02F6340150EA; Thu, 1 Mar 2018 21:05:16 +0000 (UTC) Received: from host1.jankratochvil.net (ovpn-116-55.ams2.redhat.com [10.36.116.55]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 680632144B24; Thu, 1 Mar 2018 21:05:15 +0000 (UTC) Date: Thu, 01 Mar 2018 21:05:00 -0000 From: Jan Kratochvil To: Dmitry Antipov Cc: gdb@sourceware.org Subject: Re: Add .gdb_index and CRC mismatch Message-ID: <20180301210512.GA26517@host1.jankratochvil.net> References: <25596a27-77c0-238e-748c-3d972914abec@nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <25596a27-77c0-238e-748c-3d972914abec@nvidia.com> User-Agent: Mutt/1.9.2 (2017-12-15) X-SW-Source: 2018-03/txt/msg00007.txt.bz2 On Thu, 01 Mar 2018 13:41:37 +0100, Dmitry Antipov wrote: > For the remote debugging and local copies of shared libraries, should .so CRC be affected by > adding .gdb_index as described at https://sourceware.org/gdb/onlinedocs/gdb/Index-Files.html? > After adding .gdb_index, 'target extended-remote :XXXX' refuses to load local copy with > the following message: > > warning: the debug information found in "/xxx/yyy/lib/debug/libzzz.so" does not match "target:/lib/libzzz.so" (CRC mismatch). > > If CRC was actually changed, how is it indented to use .gdb_index for the remote debugging? At least in Fedora the separate .debug files are also processed by dwz and then the CRC is updated by: /usr/lib/rpm/sepdebugcrcfix I was expecting the CRC update is needed for dwz and so gdb-add-index does not contain this functionality. But you are right it should. Besides that GDB prefers much faster verification of a .debug file match by its build-id also being used on Fedora (ld --build-id). Then sure CRC is not being checked (as that is slow to check). Jan