Peter Maydell <peter.mayd...@linaro.org> writes: > On Fri, 10 Mar 2023 at 18:00, Fabiano Rosas <faro...@suse.de> wrote: >> >> Peter Maydell <peter.mayd...@linaro.org> writes: >> >> > On Fri, 10 Mar 2023 at 10:31, Alex Bennée <alex.ben...@linaro.org> wrote: >> >> >> >> You need a very new gdb to be able to run with pauth support otherwise >> >> your likely to hit asserts and aborts. Disable pauth for now until we >> >> can properly probe support in gdb. >> >> >> >> Signed-off-by: Alex Bennée <alex.ben...@linaro.org> >> > >> > If it makes gdb fall over, then shouldn't we be disabling >> > the pauth gdbstub stuff entirely ? Otherwise even if our >> > tests are fine our users will not be... >> > >> >> Have you seem my message on IRC about changing the feature name in the >> XML? I think the issue is that we're putting the .xml in a "namespace" >> where GDB expects to only find stuff which it has code to >> support. Changing from "org.gnu.gdb.aarch64.pauth" to >> "org.qemu.aarch64.pauth" made it stop crashing and I can read the >> registers just fine. > > But then presumably a pauth-aware GDB won't actually know > the values it needs to be able to convert between with-PAC > and without-PAC addresses for backtracing? >
Good question. Although that feels to me more like a GDB feature. If we don't break it even worse by doing that, the QEMU side which is more about reading the registers should be fine. Note that we already have other .xml files using a .qemu namespace in the codebase. As I understand it, gdb simply treats these as extra registers not tied to any specific feature.
