From: Laszlo Ersek <lersek@redhat.com>
To: Bug 1498144 <1498144@bugs.launchpad.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1498144] Re: Failure booting hurd with qemu-system-i386 on ARM
Date: Wed, 23 Sep 2015 17:50:16 +0200 [thread overview]
Message-ID: <5602CA38.4080003@redhat.com> (raw)
In-Reply-To: <20150923151320.9589.84785.malone@soybean.canonical.com>
On 09/23/15 17:13, PeteVine wrote:
> 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?
>
Sorry, no idea.
next prev parent reply other threads:[~2015-09-23 15:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 19:04 [Qemu-devel] [Bug 1498144] [NEW] Failure booting hurd with qemu-system-i386 on ARM PeteVine
2015-09-21 19:23 ` [Qemu-devel] [Bug 1498144] " PeteVine
2015-09-22 19:36 ` [Qemu-devel] [Bug 1498144] [NEW] " Laszlo Ersek
2015-09-22 20:07 ` [Qemu-devel] [Bug 1498144] " PeteVine
2015-09-23 15:13 ` PeteVine
2015-09-23 15:50 ` Laszlo Ersek [this message]
2015-09-24 18:50 ` PeteVine
2015-09-24 21:00 ` PeteVine
2015-09-24 21:04 ` PeteVine
2015-10-09 23:25 ` PeteVine
2018-11-24 4:17 ` Launchpad Bug Tracker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5602CA38.4080003@redhat.com \
--to=lersek@redhat.com \
--cc=1498144@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).