From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-74.mimecast.com (us-smtp-delivery-74.mimecast.com [216.205.24.74]) by sourceware.org (Postfix) with ESMTP id 66A12385B834 for ; Mon, 30 Mar 2020 08:45:39 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 66A12385B834 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-1-Iu55JENlOcOnwRSAcww52A-1; Mon, 30 Mar 2020 04:45:32 -0400 X-MC-Unique: Iu55JENlOcOnwRSAcww52A-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id C31C5107ACC4; Mon, 30 Mar 2020 08:45:31 +0000 (UTC) Received: from host1.jankratochvil.net (ovpn-112-98.ams2.redhat.com [10.36.112.98]) by smtp.corp.redhat.com (Postfix) with ESMTPS id C3B8BDA0EA; Mon, 30 Mar 2020 08:45:25 +0000 (UTC) Date: Mon, 30 Mar 2020 10:45:22 +0200 From: Jan Kratochvil To: Norbert Lange Cc: "Frank Ch. Eigler" , gdb@sourceware.org, Gary Benson Subject: Re: Automatically fetching Build ID from remote libraries and resole them locally? Message-ID: <20200330084522.GA1075780@host1.jankratochvil.net> References: <87blohl3an.fsf@redhat.com> MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Spam-Status: No, score=-13.4 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_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:45:42 -0000 On Mon, 30 Mar 2020 10:35:30 +0200, Norbert Lange via Gdb wrote: > Currently its not possible to detect the Build ID without transferring th= e > whole library from Remote target to the local gdb. I suppose with coredum= ps > 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. Coredumps already contain build-ids of executables + shared libraries as lo= ng as it is enabled (it is by default): =09https://www.kernel.org/doc/Documentation/filesystems/proc.txt - (bit 4) ELF header pages in file-backed private memory areas (it is effective only if the bit 2 is cleared) build-id loading from remote files should be also somehow supported by rece= nt GDBs (done by Gary Benson). Fedora+RHEL GDB has patchset =09https://src.fedoraproject.org/rpms/gdb/blob/master/f/gdb-6.6-buildid-loc= ate.patch =09https://src.fedoraproject.org/rpms/gdb/blob/master/f/gdb-6.6-buildid-loc= ate-solib-missing-ids.patch =09https://src.fedoraproject.org/rpms/gdb/blob/master/f/gdb-6.6-buildid-loc= ate-core-as-arg.patch to locate appropriate executable + shared libraries from such core file by build-id - it locates then through symlinks in: =09/usr/lib/debug/.build-id/6b/6cd649300ec28b47638e766e9cbb58648cbdac{,.deb= ug} IIUC that patchset should be now being replaced by the elfutils debuginfod. Jan