[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] gdbstub.c gdb-get-register returns 0, breaking remote gdb c
From: |
Dan Kaminsky |
Subject: |
[Qemu-devel] gdbstub.c gdb-get-register returns 0, breaking remote gdb call |
Date: |
Mon, 12 Feb 2018 18:43:33 -0800 |
Unsure the scope of this bug or the proper fix, so bringing it up here
first.
gdbstub.c:gdb_read_register will return 0, and thus E14, when a remote gdb
tries to call a function in the exposed linux kernel. This appears to be
because the caller expects to be able to receive a generic register size by
calling one plus the number of known registers. However,
x86_cpu_gdb_read_register() in target/i386/gdbstub.c will only provide
register sizes for known registers, since they're not always the same.
I'm dealing with this just by shimming 8 whenever gdb_read_register returns
0, but that's obviously not correct. Suggestions?
--Dan
P.S. call still won't work unless linux is launched with noexec=off
noexec32=off, due to NX.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Qemu-devel] gdbstub.c gdb-get-register returns 0, breaking remote gdb call,
Dan Kaminsky <=