From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-il1-x12c.google.com (mail-il1-x12c.google.com [IPv6:2607:f8b0:4864:20::12c]) by sourceware.org (Postfix) with ESMTPS id ABF03385B834 for ; Mon, 30 Mar 2020 08:35:41 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org ABF03385B834 Received: by mail-il1-x12c.google.com with SMTP id x16so14929306ilp.12 for ; Mon, 30 Mar 2020 01:35:41 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=OZgxyd3e5XaD4EPPUa38dAtS2WHpOs6gB683zYseTEU=; b=sC8TMW66+byV0IsMpkObLuNuWvYByA7tzfBCMN2sj9vr6oHPa9mdjwe7B8kUrsPwda XsDae90VDleE6M7wb2TffF2oubkAdM8NPRyiqKXUnMbSTK+cNY8WPiBzgkqxpbWDuqPo rYrPoyhnhQJ4Z+Fap4ExKRkHO1yPlB/NNfHM1gcgBKAk5XFKAj0nXYlD5RxT8yUY2eDs JQ6tfszFFbOjr6XdtF9LxnDaAsdwhck5HrkhdMsVz6Q9azNQy8IMy4AXog4F2jpe4yZG OjrssoIceDpyAf0iEb3N5D7/J5MaPlvuTCVigARNiVv9/B/9gnfRSRD4KHt/OhL4xSdb hl9A== X-Gm-Message-State: ANhLgQ2s8DRpa/NgCDmn5wh8hQReveyYqM2Ly2IdkV3UDZF1tSmiAi1y 90m8wZ1LZHVL6S7Vk0ISNTyeQ15keg9OH+J3agw= X-Google-Smtp-Source: ADFU+vtG4owpZrEdzleGe/t2DG/7UxAe2PYmdSgrw9Z6mBMwPRjC7DKJakV3YfC5O16NvmxXxGOJkW7lZ+uvtQEMrcc= X-Received: by 2002:a92:774b:: with SMTP id s72mr9576336ilc.61.1585557341198; Mon, 30 Mar 2020 01:35:41 -0700 (PDT) MIME-Version: 1.0 References: <87blohl3an.fsf@redhat.com> In-Reply-To: <87blohl3an.fsf@redhat.com> From: Norbert Lange Date: Mon, 30 Mar 2020 10:35:30 +0200 Message-ID: Subject: Re: Automatically fetching Build ID from remote libraries and resole them locally? To: "Frank Ch. Eigler" Cc: gdb@sourceware.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, 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: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Mar 2020 08:35:42 -0000 Am Sa., 28. M=C3=A4rz 2020 um 01:40 Uhr schrieb Frank Ch. Eigler : > > > Norbert Lange via Gdb writes: > > > [...] > > ie. DL only some ELF headers or remotely inspect the Build-ID, > > then lookup and resolve the matching library and debuginfo in the > > debug-file-directory database. [...] > > By the way, this part of the problem is solved e.g. using the elfutils > debuginfod facility, which is now part of gdb. If gdb can get the > buildids, then it can auto-download matching binaries & source code. Yes. Just want to make sure that I am talking about the other (left) side: Remote target (gdbserver) <-> Local gdb session <-> debug file source. Currently its not possible to detect the Build ID without transferring the whole library from Remote target to the local gdb. I suppose with coredumps its a similar problem. What I would like is using build IDs wherever possible. That means retrieve them from the remote, and maybe define some fileformat to augment coredumps with the information. Norbert