From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [207.211.31.120]) by sourceware.org (Postfix) with ESMTP id 8934E385B831 for ; Mon, 6 Apr 2020 11:49:13 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 8934E385B831 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-195-L_yI75hrOpGREc6c7OhY4g-1; Mon, 06 Apr 2020 07:49:11 -0400 X-MC-Unique: L_yI75hrOpGREc6c7OhY4g-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 C4680107ACC4; Mon, 6 Apr 2020 11:49:10 +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 CE9C12708D; Mon, 6 Apr 2020 11:49:06 +0000 (UTC) Date: Mon, 6 Apr 2020 13:49:03 +0200 From: Jan Kratochvil To: Norbert Lange Cc: "Frank Ch. Eigler" , gdb@sourceware.org, Gary Benson , Sergio Durigan Junior Subject: Re: Automatically fetching Build ID from remote libraries and resole them locally? Message-ID: <20200406114903.GA2375263@host1.jankratochvil.net> References: <87blohl3an.fsf@redhat.com> <20200330084522.GA1075780@host1.jankratochvil.net> <20200330091934.GA1078028@host1.jankratochvil.net> MIME-Version: 1.0 In-Reply-To: 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-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Spam-Status: No, score=-11.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_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, 06 Apr 2020 11:49:15 -0000 On Mon, 06 Apr 2020 13:31:43 +0200, Norbert Lange wrote: > But Id have to first locate the binary manually, then starting > gdb PATH_TO_BINARY PATH_TO_CORE >=20 > Whats worse is, that gdb seems to lookup for the library first (filepath)= , > if it exists it will use the Build-Id from this potentially unrelated > version (and use the wrong debug info if one exists), > if it does not exist, then it wont even try searching in the > debug-library (neither via name or build-id). >=20 > In other words, its completely broken unless the system you debug is > the very same (and in the same state) as the executable did run on. What you describe is behaving correctly on Fedora with my off-trunk patches (I have not tested it now but I was fixing exactly this problem in its init= ial version many years ago). If you run FSF GDB maybe Red Hat should upstream m= ore of the Fedora patches. Jan