From: Lennert Buytenhek <buytenh@wantstofly.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Fedora-Core-2
Date: Wed, 4 Aug 2004 02:12:09 +0200 [thread overview]
Message-ID: <20040804001209.GA32009@xi.wantstofly.org> (raw)
In-Reply-To: <41100D95.2080405@bellard.org>
On Wed, Aug 04, 2004 at 12:11:33AM +0200, Fabrice Bellard wrote:
> The last commits should allow QEMU to work on Fedora-Core-2 without the
> published hacks. Tell me if you see improvements.
I still need setarch to get qemu-arm to run. Or is that not what
you meant? (And which commit do you mean exactly, the kernel_sigaction/
qemu_sigaction changes?)
phi% qemu-arm ./hi-arm-unknown-linux-gnu
qemu: uncaught target signal 11 (Segmentation fault) - exiting
phi% setarch i686 qemu-arm ./hi-arm-unknown-linux-gnu
hi!
phi%
diff -u bad good:
-mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xf70a4000
+mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x55001000
-mmap2(NULL, 528384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xf7023000
-mprotect(0xf70a3000, 4096, PROT_NONE) = 0
-munmap(0xf70a4000, 4096) = 0
+mmap2(NULL, 528384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x55002000
+mprotect(0x55082000, 4096, PROT_NONE) = 0
+munmap(0x55001000, 4096) = 0
---- SIGSEGV (Segmentation fault) @ 0 (0) ---
-write(2, "qemu: uncaught target signal 11 "..., 63qemu: uncaught target signal 11 (Segmentation fault) - exiting
-) = 63
-exit_group(-11) = ?
+fcntl64(0, F_GETFD) = 0
+fcntl64(1, F_GETFD) = 0
+fcntl64(2, F_GETFD) = 0
+personality(0 /* PER_??? */) = 8
+geteuid32() = 500
+getuid32() = 500
+getegid32() = 500
+getgid32() = 500
+mmap2(0x46000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, 0, 0) = 0x46000
+getpid() = 29747
+write(1, "hi!\n", 4) = 4
+exit_group(0) = ?
--L
next prev parent reply other threads:[~2004-08-04 0:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 22:11 [Qemu-devel] Fedora-Core-2 Fabrice Bellard
2004-08-03 22:36 ` Hetz Ben Hamo
2004-08-04 0:12 ` Lennert Buytenhek [this message]
2004-08-07 2:21 ` Marcelo Duarte
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=20040804001209.GA32009@xi.wantstofly.org \
--to=buytenh@wantstofly.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).