In the upcoming QEMU 2.7 we've removed the abort() call in this code
path, and instead will print an error message which hopefully is clearer
at suggesting to users where they've gone wrong rather than implying
that this is a QEMU bug:
======
qemu-system-arm: Trying to execute code outside RAM or ROM at 0x08000000
This usually means one of the following happened:
(1) You told QEMU to execute a kernel for the wrong machine type, and it
crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb
QEMU machine)
(2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a
ROM full of no-op instructions until it fell off the end
(3) Your guest kernel has a bug and crashed by jumping off into nowhere
This is almost always one of the first two, so check your command line and that
you are using the right type of kernel for this machine.
If you think option (3) is likely then you can try debugging your guest with
the -d debug options; in particular -d guest_errors will cause the log to
include a dump of the guest register state at this point.
Execution cannot continue; stopping here.
======
So I'm going to mark this bug as fix-committed, at least for upstream
QEMU.
** Changed in: qemu
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1062220
Title:
qemu-system-arm crashed with SIGABRT in cpu_abort()
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1062220/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
