This patch
https://patchew.org/QEMU/20190816233422.16715-1-...@google.com/ fixes
the issue.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1528239
Title:
Unable to debug PIE binaries with QEMU gdb s
It seems the issue is related to gdb code:
set_gdbarch_call_dummy_location (gdbarch, ON_STACK);
What is going on?
The breakpoint is stored on stack and for the first time the address has a flag
PAGE_WRITE.
After a call, the address does not have anymore the flag PAGE_WRITE. It is
changed in meth
From: Lukas Durfina
It helps to test gdb running qemu instead of a gdbserver.
It prints the same message as the gdbserver on startup.
Signed-off-by: Lukas Durfina
---
gdbstub.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/gdbstub.c b/gdbstub.c
index 8618e34311..9ad9929968 100644
--- a
I have verified the second issue: the second call of function gives error
"Cannot access memory at address".
I have tried it for various architectures. It is same for mips. But it works
for aarch64.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subsc
