From: Tom Tromey <tom@tromey.com>
To: Paul Smith via Gdb <gdb@sourceware.org>
Cc: psmith@gnu.org
Subject: Re: GDB 16.3: is it possible to cross-debug an x64 core from ARM?
Date: Mon, 01 Dec 2025 12:53:07 -0700 [thread overview]
Message-ID: <87ms429dy4.fsf@tromey.com> (raw)
In-Reply-To: <2f8e6564c0110db9be7ed9b5ab78ee5c9349ca0a.camel@gnu.org> (Paul Smith via Gdb's message of "Mon, 01 Dec 2025 10:36:17 -0500")
>>>>> "Paul" == Paul Smith via Gdb <gdb@sourceware.org> writes:
Paul> But, if I try to build an aarch64 GDB (on an ARM system) that has
Paul> support for debugging x86_64 core files, the build fails like this:
Paul> $ ../gdb-6.3/configure ... --enable-targets=x86_64-linux-gnu
Paul> ...
Paul> $ make -j$(nprocs)
Paul> ...
Paul> make[2]: *** No rule to make target '../sim/aarch64/libsim.a', needed by 'gdb'. Stop.
Either the sim should be auto-disabled when it isn't available for the
port, or it should build and be linked in. So one way or another this
is a bug. Is the sim code built for you?
FWIW I normally use --enable-targets=all so I'm usually seeing all the
sims be built (though only one can be linked in).
A workaround for you would be to disable the sims, aka --disable-sim.
However it would be better to find out what's really gone wrong.
Tom
next prev parent reply other threads:[~2025-12-01 19:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 15:36 Paul Smith via Gdb
2025-12-01 19:53 ` Tom Tromey [this message]
2025-12-01 20:19 ` Simon Marchi via Gdb
2025-12-01 21:13 ` Simon Marchi via Gdb
2025-12-03 13:13 ` Paul Smith via Gdb
2025-12-05 19:10 ` Luis via Gdb
2025-12-05 22:40 ` Paul Smith via Gdb
2025-12-07 18:41 ` Luis via Gdb
2025-12-08 18:08 ` Paul Smith via Gdb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ms429dy4.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb@sourceware.org \
--cc=psmith@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox