Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Luis via Gdb <gdb@sourceware.org>
To: psmith@gnu.org
Cc: gdb@sourceware.org
Subject: Re: GDB 16.3: is it possible to cross-debug an x64 core from ARM?
Date: Sun, 7 Dec 2025 18:41:48 +0000	[thread overview]
Message-ID: <81fb930a-7519-4d41-850a-6e90af5dc607@gmail.com> (raw)
In-Reply-To: <433e43213ec07327632e874350cce49f6caaa5a7.camel@gnu.org>

On 05/12/2025 22:40, Paul Smith wrote:
> On Fri, 2025-12-05 at 19:10 +0000, Luis wrote:
>> To be honest, the aarch64 sim is very outdated. I'm not sure why we
>> still carry it around.
> 
> Well, it's built if you configure GDB with --enable-targets holding
> aarch64-linux-gnu, and if you don't use that configure option then you
> can't cross-debug ARM cores on non-ARM systems.

I usually build gdb with --enable-targets=all to get all the ports. I 
also disable all the sims with what Tom suggested (--disable-sim).

> 
> If you're suggesting that it should be possible to cross-debug for ARM
> without that sim, I can't speak to that.

Cross-debugging should work without building the simulators, and I´d 
recommend doing that so you don´t build more than required.

What I was suggesting (not specifically to you, but as an idea) is that 
we (as a project) ought to think about removing the aarch64 simulator as 
it is very stale.

> 
> Cheers!


  reply	other threads:[~2025-12-07 18:42 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
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 [this message]
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=81fb930a-7519-4d41-850a-6e90af5dc607@gmail.com \
    --to=gdb@sourceware.org \
    --cc=luis.machado.foss@gmail.com \
    --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