From: Yodel Eldar <yodel.eldar@gmail.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Simon Marchi <simark@simark.ca>,
gdb-patches@sourceware.org, Yodel Eldar <yodel.eldar@gmail.com>
Subject: Re: [PATCH 1/2] gdb/alpha: Add target description support
Date: Wed, 4 Jun 2025 12:29:34 -0500 [thread overview]
Message-ID: <3ef4c598-28d8-4c66-844d-58e5629415ab@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2506041539500.1790@angie.orcam.me.uk>
On 6/4/25 9:49 AM, Maciej W. Rozycki wrote:
> On Wed, 4 Jun 2025, Yodel Eldar wrote:
>
>>> Do we need to call tdesc_numbered_register for the register whose name
>>> is ""? I suppose that we do, for backwards compatibility, when
>>> debugging against a remote target that doesn't send a target
>>> description?
>> Hi Simon and thanks for your time and question! I think we do, because
>> (IIUC) suppose an older remote target responds to, say, a 'p n' packet,
>> but the anonymous register is unaccounted for by the client, wouldn't
>> that break compatibility? Can't say for certain, so I defer to your and
>> the community's wisdom and err on the side of caution as I investigate
>> it.
> Are there any remote Alpha targets there in the first place?
>
> I only have writing Alpha/Linux gdbserver on my todo list once I'm done
> with the more urgent Alpha stuff (Linux kernel EV4 support restoration,
> GCC LRA conversion) and I haven't heard of any other Alpha GDB RSP debug
> stub either. There *might* be something in QEMU; I guess that'd be the
> only place to check.
>
> Maciej
>
Maciej, you hit the nail on the head! Indeed, QEMU is the project I
alluded to in the cover letter for the patch, and I have been using it
for testing throughout the development of the patch. It also provided
the impetus to write the target description for Alpha in the first
place as it uses them for its execlog plugin.
Thanks for taking the time to reply despite having more pressing
Alpha tasks. I will keep an eye out for your forthcoming submissions,
and provide my modest feedback if it's helpful.
Yodel
next prev parent reply other threads:[~2025-06-04 17:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 15:12 [PATCH 0/2] gdb/alpha: Add target description support and fpcr flags Yodel Eldar
2025-05-26 15:12 ` [PATCH 1/2] gdb/alpha: Add target description support Yodel Eldar
2025-05-26 16:13 ` Eli Zaretskii
2025-05-26 17:14 ` Yodel
2025-06-03 18:49 ` Simon Marchi
2025-06-04 13:44 ` Yodel Eldar
2025-06-04 14:49 ` Maciej W. Rozycki
2025-06-04 17:29 ` Yodel Eldar [this message]
2025-06-12 19:29 ` Yodel Eldar
2025-06-12 20:30 ` Simon Marchi
2025-06-12 20:33 ` Simon Marchi
2025-06-12 22:07 ` Yodel Eldar
2025-06-13 14:34 ` Simon Marchi
2025-06-30 0:08 ` Yodel Eldar
2025-07-02 17:14 ` Simon Marchi
2025-07-02 18:51 ` Yodel Eldar
2025-07-02 18:53 ` Maciej W. Rozycki
2025-07-02 19:02 ` Simon Marchi
2025-07-02 19:21 ` Maciej W. Rozycki
2025-07-02 20:52 ` Yodel Eldar
2025-07-02 21:12 ` Maciej W. Rozycki
2025-07-03 16:49 ` Yodel Eldar
2025-07-03 16:02 ` Simon Marchi
2025-07-02 18:48 ` Maciej W. Rozycki
2025-05-26 15:12 ` [PATCH 2/2] gdb/alpha: Redefine fpcr with fpcr_flags type Yodel Eldar
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=3ef4c598-28d8-4c66-844d-58e5629415ab@gmail.com \
--to=yodel.eldar@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=macro@orcam.me.uk \
--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