From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id ODEwEY1Qx2CQQQAAWB0awg (envelope-from ) for ; Mon, 14 Jun 2021 08:50:21 -0400 Received: by simark.ca (Postfix, from userid 112) id 441511F163; Mon, 14 Jun 2021 08:50:21 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,RDNS_DYNAMIC,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (ip-8-43-85-97.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 89D031E813 for ; Mon, 14 Jun 2021 08:50:20 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 03B4F3835434 for ; Mon, 14 Jun 2021 12:50:20 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 03B4F3835434 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1623675020; bh=xBtUMb9t7yhWofwVtRSXSfcR8klOyl5PRxs5atbqlsA=; h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=oDKGHVaWM4CG30wSb873iMi/Xx+NzgzGz0s1mirWo/MYeFR/5CPI3VZzBmjoNhmu6 MNrmH3ScUU/1winB7OZ0pQcmXwPkwve4kqm/e6qNHnvWoXCNyi3Nbq08cXbwE5kVg8 7JlYaZcXDUKXCRKllG1kUnrAKTduqQZRon9n3vXE= 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 628D0388A413 for ; Mon, 14 Jun 2021 12:49:28 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 628D0388A413 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-283-B3QnrrGNPnGE4Dvf1fesYQ-1; Mon, 14 Jun 2021 08:49:25 -0400 X-MC-Unique: B3QnrrGNPnGE4Dvf1fesYQ-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 8666C91272; Mon, 14 Jun 2021 12:49:23 +0000 (UTC) Received: from redhat.com (ovpn-112-13.phx2.redhat.com [10.3.112.13]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 476055C22B; Mon, 14 Jun 2021 12:49:23 +0000 (UTC) Received: from fche by redhat.com with local (Exim 4.94.2) (envelope-from ) id 1lsm1p-0000wX-0h; Mon, 14 Jun 2021 08:49:21 -0400 Date: Mon, 14 Jun 2021 08:49:20 -0400 To: Matt Schulte Subject: Re: build-ids, .debug_sup and other IDs (Was: [PATCH] Handle DWARF 5 separate debug sections) Message-ID: <20210614124920.GD3758@redhat.com> References: <20210221231810.1062175-1-tom@tromey.com> <20210224150752.GA23884@tarox.wildebeest.org> <8c0ada00-7516-a7a2-b08e-aaaf677dd4f6@redhat.com> <20210224172101.GB3014@wildebeest.org> MIME-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.12.0 (2019-05-25) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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: , From: "Frank Ch. Eigler via Gdb-patches" Reply-To: "Frank Ch. Eigler" Cc: dwz@sourceware.org, Nick Clifton , Mark Wielaard , Tom Tromey , elfutils-devel@sourceware.org, gdb-patches@sourceware.org Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" Hi - > I'm concerned about using dwo IDs to index debuginfod. They are only > 64-bits and there will be many more dwo IDs than build ids or > supplemental file ids [...] AIUI, -gsplit-dwarf is more suitable for development/scratch builds than for distro binaries. If distros agree, then I would not expect .dwo files to show up in distro-wide debuginfod services, but rather within developers' own build trees. Then debuginfod indexing collisions would only be a risk within a particular local set of trees (if serviced by a local debuginfod), rather than distro wide or wider. > What about using `/buildid/BUILDID/dwp` instead? This is not a > perfect solution, since (currently) no one puts the build-id into > the *.dwp file, but it does get around this collision problem. The hypothetical problem is collision between dwo/dwp files, not between dwo/dwp and normal buildid dwarf files, right? In that case, are you talking about two levels of indexing (buildid of final linked binary + dwo_id)? That would resemble the indexing work required from debuginfod to match up binaries with their source files plus binaries with dwz supplemental files). - FChE