From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id gfdELQDmCGjUcAEAWB0awg (envelope-from ) for ; Wed, 23 Apr 2025 09:07:12 -0400 Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=X4lkBJyX; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id A4F601E0C3; Wed, 23 Apr 2025 09:07:12 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-5.4 required=5.0 tests=ARC_SIGNED,ARC_VALID,BAYES_00, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED autolearn=ham autolearn_force=no version=4.0.1 Received: from server2.sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id AD9981E0C0 for ; Wed, 23 Apr 2025 09:07:05 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 3C6BC3857BB9 for ; Wed, 23 Apr 2025 13:07:05 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3C6BC3857BB9 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1745413625; bh=QKKD4eMneVTD0sSTtSfYAqgTu5hqu2tdNB6dADk8Kyg=; h=Date:To:Subject:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:From:Reply-To:From; b=X4lkBJyXZ+d7QVvdDtrBLgBzaDQ8n2VeNVLOEeWKLpvcbOlrt0a3JX3qVhZQBmZht lIsUiNVyJitFch8f9rPTPVDfZBkxVabSoTSJ9a9W+3LqvcvDhauYN11wR5gJPaMoqx DAsK24azpWNI6camakp8+y9YMiskkFQe02QU37/Q= Received: from mail.viric.name (mail.viric.name [37.18.133.75]) by sourceware.org (Postfix) with ESMTPS id 2DB3A3858D35 for ; Wed, 23 Apr 2025 13:06:13 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 2DB3A3858D35 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 2DB3A3858D35 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1745413573; cv=none; b=x1jgsEQ6QCtoG3DAG1vdkccmtQhpynivpwhnojv3l9IQUKD+CszpC2XbUPBqu/Py/Kwx1MuIFPMfnu/Cc8gRbHZoCgf29k4w2et32m5eGBXd3aynSa5sNTyicm/O8jYFTC+nLDwo0oOQCktl99GQRVtoQxsC3FlLLk4CNIu9QrY= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1745413573; c=relaxed/simple; bh=Af2tSn0fLhOliQscZNoBe+9ywicVIEpGIGIXVRQ8o08=; h=DKIM-Signature:Date:From:To:Subject:Message-ID:MIME-Version; b=H0cW4nsd+3HZSx+UKitmfb06W2iot7HjP5mu9jVqjtA1lYowdoPLev97q04y/f22lUmidzMOxUuCOY+GId7na3BGmpCuhcsXeiUkwqEM8bY1ByT4n/eazsJAMbWcTgksv5kjke3PIOW97CoxOkdI1Y8a3eDOoUYdiw0Kzk322jc= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2DB3A3858D35 Received: by mail.viric.name (Postfix, from userid 1000) id EA2AB1AA4287; Wed, 23 Apr 2025 15:06:11 +0200 (CEST) Date: Wed, 23 Apr 2025 15:06:11 +0200 To: gdb@sourceware.org Subject: sysroot and coredump debugging Message-ID: X-Accept-Language: ca, es, eo, ru, en, jbo, tokipona MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: =?utf-8?q?Llu=C3=ADs_Batlle_i_Rossell_via_Gdb?= Reply-To: =?utf-8?B?TGx1w61z?= Batlle i Rossell Errors-To: gdb-bounces~public-inbox=simark.ca@sourceware.org Sender: "Gdb" Hello, I have an target system, for which I have a sysroot path in my development computer. Both GNU/Linux. I expect that I can run this in my development computer, after downloading the core dump from the target system: (gdb) set sysroot /mysysroot (gdb) file myelf # it has debug info (gdb) core-file core And this never works; it drops the file with the symbols, thinking it's unrelated to the core dump: warning: Can't open file /home/user/myelf during file-backed mapping note processing warning: core file may not match specified executable file. Nothing works with dynamic libs loaded either. The only way I can make gdb to allow me to debug the core dump with symbols is by copying the elf to "/mysysroot/home/user/myelf", as it was in the target system. Is this expected? It is very annoying. Why should the elf of the executable sit within the sysroot in an exact place, to debug a core dump? I use gdb 15.2 but this happens at least since gdb 11. Maybe it is fixed in a newer version? Thank you, Lluís.