From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by sourceware.org (Postfix) with ESMTP id 4F7263857003 for ; Thu, 25 Feb 2021 17:04:48 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 4F7263857003 Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-493-SMiZ5NMRPDyJSPZNNpUdvw-1; Thu, 25 Feb 2021 12:04:44 -0500 X-MC-Unique: SMiZ5NMRPDyJSPZNNpUdvw-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 886DC10082F8; Thu, 25 Feb 2021 17:04:42 +0000 (UTC) Received: from redhat.com (ovpn-112-160.phx2.redhat.com [10.3.112.160]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 67BDA19D9C; Thu, 25 Feb 2021 17:04:42 +0000 (UTC) Received: from fche by redhat.com with local (Exim 4.94) (envelope-from ) id 1lFK48-0003zI-Fg; Thu, 25 Feb 2021 12:04:40 -0500 Date: Thu, 25 Feb 2021 12:04:40 -0500 From: "Frank Ch. Eigler" To: Jakub Jelinek Cc: Tom Tromey , Mark Wielaard , dwz@sourceware.org, elfutils-devel@sourceware.org, gdb-patches@sourceware.org Subject: Re: build-ids, .debug_sup and other IDs Message-ID: <20210225170440.GD11313@redhat.com> References: <20210221231810.1062175-1-tom@tromey.com> <20210224150752.GA23884@tarox.wildebeest.org> <87a6rt1b12.fsf@tromey.com> <20210225164245.GC11313@redhat.com> <20210225164840.GJ4020736@tucnak> MIME-Version: 1.0 In-Reply-To: <20210225164840.GJ4020736@tucnak> User-Agent: Mutt/1.12.0 (2019-05-25) X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, 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: dwz@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Dwz mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Feb 2021 17:04:49 -0000 Hi - > For dwz --dwarf-5, if it produced a .note.gnu.build-id, it would produce > the same one, but I thought that if I produced that, then consumers could > keep using that instead of .debug_sup which is the only thing defined > in the standard, so in the end dwz --dwarf-5 only produces .debug_sup > on both the referrers side and on the side of supplemental object file > as DWARF specifies. Right, but build-ids are still in normal binaries -- just not the dwz-commonized files created by "dwz --dwarf-5"? So our toolchains still process build-ids routinely for all the other uses. By omitting the build-id on the dwz-generated files, we're forcing a flag day on all our consumer tools. (Does dwz'd dwarf5 even work on gdb etc. now?) ISTM tool backward compatibility is more important, so I would suggest dwz generate -both- identifiers. - FChE