[Bug 1774149] Re: qemu-user x86_64 x86 gdb call function from gdb doesn't work

2021-06-21 Thread Launchpad Bug Tracker
[Expired for QEMU because there has been no activity for 60 days.] ** Changed in: qemu Status: Incomplete => Expired -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1774149 Title: qemu-user x

[Bug 1774149] Re: qemu-user x86_64 x86 gdb call function from gdb doesn't work

2021-04-21 Thread Thomas Huth
The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to "Incomplete" now. If you still think this bug report here is valid, then please switch the

[Qemu-devel] [Bug 1774149] Re: qemu-user x86_64 x86 gdb call function from gdb doesn't work

2019-07-01 Thread Lukas Durfina
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

[Qemu-devel] [Bug 1774149] Re: qemu-user x86_64 x86 gdb call function from gdb doesn't work

2019-06-07 Thread Lukas Durfina
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