From: Luis Machado <luis.machado@linaro.org>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: [RFC] Changing gdbarch mid-execution
Date: Mon, 06 Jan 2020 14:08:00 -0000 [thread overview]
Message-ID: <4f30e9b5-d196-1dc5-7713-6c42e7d9494d@linaro.org> (raw)
Hi,
I have a situation at hand and i'm thinking about how to best solve it.
AArch64 SVE has the capability of changing the vector length
mid-execution. This can be done at the thread level.
Native GDB already supports this by looking at the ptrace data. But
doing this for a remote target requires changes to the RSP.
Instead of changing things just for this particular case, i'm
considering having a more general mechanism for updating the
architecture data whenever such change is noticed by whoever is
controlling the inferior.
My idea is to get the mechanism started by using the stop reply to send
a new notification, say, "arch-changed".
That should trigger GDB to re-fetch the architecture data and
reinitialize it.
In the particular case of SVE, we only need to fetch the target
description again, so we have the proper vector length and data types set.
Does this sound like a useful feature? Or should i go for the solution
with less impact that will only take care of re-fetching the target
description?
Regards,
Luis
next reply other threads:[~2020-01-06 14:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 14:08 Luis Machado [this message]
2020-01-22 14:56 ` Pedro Alves
2020-01-22 17:03 ` Luis Machado
2020-01-22 17:04 ` Luis Machado
2020-01-24 14:06 ` Alan Hayward
2020-01-23 16:06 ` Pedro Alves
2020-01-28 19:21 ` Luis Machado
2020-01-28 19:32 ` Tim Newsome
2020-01-28 19:40 ` Luis Machado
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=4f30e9b5-d196-1dc5-7713-6c42e7d9494d@linaro.org \
--to=luis.machado@linaro.org \
--cc=gdb@sourceware.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