From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id /K/IFRe2LWmOrAsAWB0awg (envelope-from ) for ; Mon, 01 Dec 2025 10:36:55 -0500 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=EZDnGEzP; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id 3B8F71E08D; Mon, 01 Dec 2025 10:36:55 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-0.1 required=5.0 tests=ARC_SIGNED,ARC_VALID,BAYES_00, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED,RCVD_IN_VALIDITY_RPBL_BLOCKED, RCVD_IN_VALIDITY_SAFE_BLOCKED autolearn=no autolearn_force=no version=4.0.1 Received: from sourceware.org (vm01.sourceware.org [38.145.34.32]) (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 8CED31E08D for ; Mon, 01 Dec 2025 10:36:54 -0500 (EST) Received: from vm01.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 232D548FD862 for ; Mon, 1 Dec 2025 15:36:54 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 232D548FD862 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1764603414; bh=b9qGVC0fJ9jnRIB7qboGdrQd4hugxLvvMHcbyowbq0I=; h=Subject:To:Date:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:From:Reply-To:From; b=EZDnGEzP25cTU4bzHw3/Sev18HH6ReM+RJbUyml/ykobLHskwR3/6SQpvudHbyDNp e/O6IczEAosblAlCggj77sUwoU1+GksEv5TW6ClgkJE7dS6M1V7ly8Q9yvMzNcQbVK UOfMG/1DI/o+6cPaHAUx5Edp7EQkR2sZgPA5+sAs= Received: from eggs.gnu.org (eggs.gnu.org [209.51.188.92]) by sourceware.org (Postfix) with ESMTPS id 1E58748FDCAD for ; Mon, 1 Dec 2025 15:36:20 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 1E58748FDCAD ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 1E58748FDCAD ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1764603380; cv=none; b=pmYWNHmCr+EQ6neFCdc1qZRWHCmX6XxSYmJYSg990DANKBiVQIRU4ncN9N0KNkWk7PWjxCgv7DJlWmzEGgePX4BuY5XdzcZN6bjG44kZqGICtzLqDvPp3ceY9asy4GxOPESDR+rTIql/8KZLZGcsofcZpGgCVepnpJ8fKBnWpoQ= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1764603380; c=relaxed/simple; bh=k+uV7T7YlrP4QF6c0/rrSZNxVysepN5tkwyNRORkJwo=; h=DKIM-Signature:Message-ID:Subject:From:To:Date:MIME-Version; b=D2jmex0ICH9/3qDQZUhzmyKm48TDqJH2iWZo3MDe9m2uJJarIWuRQqa+ZqjFG/v8NAeICwoWWqq/Imjre1T4n0AfXzMJjIM399+83Mhb6emIgMl9Nq++dxYKFzFsgeXe7DlBGR7XOab7YFk+EXIS4GVCBuEhKhV4Wi4TXZbsep8= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1E58748FDCAD Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1vQ5wp-0003Zo-HU for gdb@sourceware.org; Mon, 01 Dec 2025 10:36:19 -0500 Message-ID: <2f8e6564c0110db9be7ed9b5ab78ee5c9349ca0a.camel@gnu.org> Subject: GDB 16.3: is it possible to cross-debug an x64 core from ARM? To: gdb@sourceware.org Date: Mon, 01 Dec 2025 10:36:17 -0500 Organization: GNU's Not UNIX! Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.58.2 (by Flathub.org) MIME-Version: 1.0 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: Paul Smith via Gdb Reply-To: psmith@gnu.org Errors-To: gdb-bounces~public-inbox=simark.ca@sourceware.org Sender: "Gdb" If I build an x86_64 GDB binary that has support for debugging ARM core files, it works fine. The build is invoked (on x86_64) like: $ ../gdb-6.3/configure ... --enable-targets=3Daarch64-linux-gnu ... $ make -j$(nproc) There's no problem and the resulting GDB works both for native x86_64 cores and ARM cores. But, if I try to build an aarch64 GDB (on an ARM system) that has support for debugging x86_64 core files, the build fails like this: $ ../gdb-6.3/configure ... --enable-targets=3Dx86_64-linux-gnu ... $ make -j$(nprocs) ... make[2]: *** No rule to make target '../sim/aarch64/libsim.a', needed by = 'gdb'. Stop. If I use the same configure arguments but omitting --enable-targets then I get a correctly built GDB that will work on ARM. Comparing sim/config.log from the ARM build without --enable-targets (which works) versus the failing one, shows nothing too interesting; I get the same messages etc. The only consequential difference is that in the working version (no extra enabled targets) I see: SIM_ENABLE_ARCH_aarch64_FALSE=3D'#' SIM_ENABLE_ARCH_aarch64_TRUE=3D'' while in the failing version (with x86_64 enabled target) I see: SIM_ENABLE_ARCH_aarch64_FALSE=3D'' SIM_ENABLE_ARCH_aarch64_TRUE=3D'#' Which could have been guessed from the error message I suppose :). Anyone have any further advice? I guess the next step would be to run configure with sh -x and see if I can deduce where it gets confused (assuming this is a supported configuration).