[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1498144] Re: Failure booting hurd with qemu-system-i38
From: |
PeteVine |
Subject: |
[Qemu-devel] [Bug 1498144] Re: Failure booting hurd with qemu-system-i386 on ARM |
Date: |
Wed, 23 Sep 2015 15:13:20 -0000 |
I can't get any more useful info - either the script is expecting some
outdated version of python or there's simply nothing else to see cause
qemu failed to start.
For example:
(gdb) source qemu-gdb.py
(gdb) run
Starting program: /usr/bin/qemu-system-i386 -m 512 -hda
/media/odroid/debian-hurd-20150320.img
and so on
(gdb) qemu mtree
Python Exception <class 'gdb.error'> No symbol "address_space_memory" in
current context.:
Error occurred in Python command: No symbol "address_space_memory" in current
context.
As for using:
qemu coroutine, I'm not sure where the pointer value should come from
but feeding it a bogus one ends exactly as above.
Any suggestions?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1498144
Title:
Failure booting hurd with qemu-system-i386 on ARM
Status in QEMU:
New
Bug description:
Trying to boot debian-hurd-20150320.img ends with:
qemu-system-i386: qemu-coroutine-lock.c:91: qemu_co_queue_restart_all:
Assertion `qemu_in_coroutine()' failed.
Program received signal SIGABRT, Aborted.
__libc_do_syscall ()
at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44
44 ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S: No such file
or directory.
(gdb) bt
#0 __libc_do_syscall ()
at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44
#1 0xb6ef8f0e in __GI_raise (address@hidden)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#2 0xb6efb766 in __GI_abort () at abort.c:89
#3 0xb6ef4150 in __assert_fail_base (
fmt=0x1 <error: Cannot access memory at address 0x1>,
assertion=0x7f89a234 "qemu_in_coroutine()", address@hidden,
file=0x7f89da58 "qemu-coroutine-lock.c", address@hidden "\001",
line=91, address@hidden,
address@hidden "qemu_co_queue_restart_all")
at assert.c:92
#4 0xb6ef41e6 in __GI___assert_fail (assertion=0x0, file=0xb5660000 "\001",
line=3069931692, function=0x7f89ab78 "qemu_co_queue_restart_all")
at assert.c:101
#5 0x7f59a6b4 in ?? ()
I was using the same setup as in Bug 893208 (i.e git checkout from
2015-09-15, armv7 Odroid C1)
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1498144/+subscriptions
- [Qemu-devel] [Bug 1498144] [NEW] Failure booting hurd with qemu-system-i386 on ARM, PeteVine, 2015/09/21
- [Qemu-devel] [Bug 1498144] Re: Failure booting hurd with qemu-system-i386 on ARM, PeteVine, 2015/09/21
- Re: [Qemu-devel] [Bug 1498144] [NEW] Failure booting hurd with qemu-system-i386 on ARM, Laszlo Ersek, 2015/09/22
- [Qemu-devel] [Bug 1498144] Re: Failure booting hurd with qemu-system-i386 on ARM, PeteVine, 2015/09/22
- [Qemu-devel] [Bug 1498144] Re: Failure booting hurd with qemu-system-i386 on ARM,
PeteVine <=
- [Qemu-devel] [Bug 1498144] Re: Failure booting hurd with qemu-system-i386 on ARM, PeteVine, 2015/09/24
- [Qemu-devel] [Bug 1498144] Re: Failure booting hurd with qemu-system-i386 on ARM, PeteVine, 2015/09/24
- [Qemu-devel] [Bug 1498144] Re: Failure booting hurd with qemu-system-i386 on ARM, PeteVine, 2015/09/24