From: Luis via Gdb <gdb@sourceware.org>
To: psmith@gnu.org
Cc: Simon Marchi <simark@simark.ca>, gdb@sourceware.org
Subject: Re: GDB 16.3: is it possible to cross-debug an x64 core from ARM?
Date: Fri, 5 Dec 2025 19:10:24 +0000 [thread overview]
Message-ID: <CANnS9rs0dnWXr_4_0-9VgsHtDP0632Nbv0LKhZR5zXc6U4AVjQ@mail.gmail.com> (raw)
In-Reply-To: <06f0c692e3392a1040506f17929b42fd9a863ed4.camel@gnu.org>
To be honest, the aarch64 sim is very outdated. I'm not sure why we still
carry it around.
On Wed, Dec 3, 2025, 13:14 Paul Smith via Gdb <gdb@sourceware.org> wrote:
> On Mon, 2025-12-01 at 16:13 -0500, Simon Marchi wrote:
> > I think I found the problem:
> >
> > https://gitlab.com/gnutools/binutils-gdb/-
> > /blob/887bcaf98ea8e1ef76f6dd429b01b5258a782172/sim/configure.ac#L73
> >
> > We essentially do:
> >
> > for targ in aarch64-unknown-linux-gnu x86_64-linux-gnu; do
> > // try to match $targ against all known targets
> > done
>
> Thanks, I was in the middle of looking at that when I got your email :)
>
> I submitted a patch to fix this:
> https://sourceware.org/pipermail/gdb-patches/2025-December/223119.html
>
> I did it a different way than the simplest option, but that to me seems
> safer and more reliable. I tried to keep with the same style used in
> other sh code in configure.ac.
>
next prev parent reply other threads:[~2025-12-05 19:11 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 [this message]
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=CANnS9rs0dnWXr_4_0-9VgsHtDP0632Nbv0LKhZR5zXc6U4AVjQ@mail.gmail.com \
--to=gdb@sourceware.org \
--cc=luis.machado.foss@gmail.com \
--cc=psmith@gnu.org \
--cc=simark@simark.ca \
/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