From: David Woodhouse <dwmw2@infradead.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] ARM in big endian mode?
Date: Mon, 12 Jul 2004 00:17:27 +0100 [thread overview]
Message-ID: <1089587847.4217.10.camel@localhost.localdomain> (raw)
In-Reply-To: <20040704115730.GA21047@xi.wantstofly.org>
On Sun, 2004-07-04 at 13:57 +0200, Lennert Buytenhek wrote:
> % ./qemu-arm ./x
> qemu: uncaught target signal 11 (Segmentation fault) - exiting
Are you sure that's happening only for BE ARM binaries? I have a vague
recollection that last time I tried qemu-arm it was doing that even for
LE executables.
--
dwmw2
next prev parent reply other threads:[~2004-07-11 23:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-03 16:03 [Qemu-devel] ARM in big endian mode? Lennert Buytenhek
2004-07-04 11:30 ` Gianni Tedesco
2004-07-04 11:57 ` Lennert Buytenhek
2004-07-11 23:17 ` David Woodhouse [this message]
2004-07-11 23:43 ` Lennert Buytenhek
2004-08-06 14:55 ` David Woodhouse
2004-08-06 15:59 ` [PROBLEM FOUND] qemu-arm on FC2 (was: Re: [Qemu-devel] ARM in big endian mode?) Lennert Buytenhek
2004-08-06 16:31 ` David Woodhouse
2004-08-06 17:18 ` Lennert Buytenhek
2004-07-04 13:11 ` [Qemu-devel] ARM in big endian mode? Fabrice Bellard
2004-07-04 13:28 ` Lennert Buytenhek
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=1089587847.4217.10.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--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).