[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/1856837
Title:
qemu 4.2.0
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
Thanks, this helps a lot! We will now check the code again and see what
causes the behaviour.
Fabian
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1856837
Title:
qemu 4.2.0 arm segmentation fault
At the point of the segfault, QEMU is correctly delivering a segfault to
the guest because it has attempted to dereference a NULL pointer. You
can see this if you run QEMU with the '-g 1234' option and connect an
arm-aware gdb to it:
(gdb) disas $pc-32,$pc+32
Dump of assembler code from 0x2bf24c t
Sorry for the delay. I added the sysroot, the binary and the files causing the
segfault.
Please let me know if there is something missing.
I used the following commands to let it run:
export LD_LIBRARY_PATH=/opt/qemu-test/test1/lib
/opt/qemu-test/test1/bin/qemu-arm "/opt/qemu-test/test1/files/mk
Can you provide a repro case (attach binary/etc to the bug) so we can
investigate?
Note that QEMU will produce that segfault message both for bugs in QEMU
(where it unexpectedly segfaults) but also for bugs in the guest binary
itself where we're correctly emulating "guest did something causing a
s
