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 [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id B6C653858016 for ; Wed, 28 Sep 2022 14:28:22 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org B6C653858016 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1664375302; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=AxmJawADgPWcl26nCHnsUqiSt+1486WAgK8MFxvf7g8=; b=KZ8U9EcJnc1NwC9lYBOzym5FT9S/t8z0Ok2PRihx9XjnsI4dJxFn3D95gKQXZUqsaN/O8G 5kozsMKd1qpJfZIkrt8ASQV5FXpXCXfCr4tJxJy14z08J6ZLgusb9nWc1FJOzYeoqVzwl6 6jGNzeIKhKu8izjp8Zpmblv7ABBAfT4= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-462-CFv_oN_vMmezOlT1VYV_Ew-1; Wed, 28 Sep 2022 10:28:20 -0400 X-MC-Unique: CFv_oN_vMmezOlT1VYV_Ew-1 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 mimecast-mx02.redhat.com (Postfix) with ESMTPS id 725692999B59 for ; Wed, 28 Sep 2022 14:28:20 +0000 (UTC) Received: from redhat.com (unknown [10.2.17.198]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 637392166B47; Wed, 28 Sep 2022 14:28:20 +0000 (UTC) Received: from fche by redhat.com with local (Exim 4.94.2) (envelope-from ) id 1odY2s-0002kd-Fg; Wed, 28 Sep 2022 10:28:18 -0400 Date: Wed, 28 Sep 2022 10:28:18 -0400 From: "Frank Ch. Eigler" To: Aaron Merey Cc: elfutils-devel@sourceware.org Subject: Re: [PATCH] debuginfod: Support queries for ELF/DWARF sections. Message-ID: <20220928142818.GH7916@redhat.com> References: <20220928021052.315981-1-amerey@redhat.com> MIME-Version: 1.0 In-Reply-To: <20220928021052.315981-1-amerey@redhat.com> User-Agent: Mutt/1.12.0 (2019-05-25) X-Scanned-By: MIMEDefang 3.1 on 10.11.54.6 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=-9.0 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi, Aaron - On Tue, Sep 27, 2022 at 10:10:52PM -0400, Aaron Merey via Elfutils-devel wrote: > [...] In order to distinguish between debuginfo and executable > files with the same build-id, this function includes a bool > parameter use_debuginfo. If true, attempt to retrieve the section > from the debuginfo file with the given build-id. If false, use the > executable instead. [...] How would a client know which one to use? Does it provide power or benefit to force them to choose (or iterate?). Is there a scenario where the content could be different between the two (if both existed)? If that decisionmaking is not warranted to put upon the shoulders of the client, the server could just be asked for a section name "as if from an unstripped executable", and let it find that in the executable or debuginfo, whereever. > [...] Although this patch does not implement it, we could generate > .gdb_index on-the-fly if the target file does not contain it. > However for large debuginfo files generating the index can take a > non-trivial amount of time (ex. about 25 seconds for a 2.5GB > debuginfo file). [...] Even that is not too bad, considering that the alternative would be having to download that 2.5GB file. I recall you saying that on some distros, gdb-index sections are always there anyway, so we wouldn't have to rush to implement this feature. - FChE