From: Stefan Weil <sw@weilnetz.de>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [Bug] qemu-sparc64 broken
Date: Thu, 05 Sep 2013 22:35:35 +0200 [thread overview]
Message-ID: <5228EB17.4050209@weilnetz.de> (raw)
Here is the result of running Debian's busybox-static for sparc64:
$ sparc64-linux-user/qemu-sparc64 /usr/gnemul/qemu-sparc64/bin/busybox
ls -l block.c
?rwxr-x--T 1 stefan root 1378329541 Jan 1 1970 block.c
It's obviously wrong. All other user emulations return the correct result:
$ busybox ls -l block.c
-rw-r--r-- 1 stefan stefan 131462 Sep 3 21:13 block.c
In a first analysis of this, I noticed that it is impossible to run
qemu-sparc64
under gdb (raised fatal signal). I was also surprised to see that
target_stat64
is unused.
Regards,
Stefan
next reply other threads:[~2013-09-05 20:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 20:35 Stefan Weil [this message]
2013-09-05 21:32 ` [Qemu-devel] [Bug] qemu-sparc64 broken Peter Maydell
2013-09-06 4:53 ` Stefan Weil
2013-09-06 15:12 ` Richard Henderson
2013-09-06 15:15 ` Peter Maydell
2013-09-06 15:20 ` Richard Henderson
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=5228EB17.4050209@weilnetz.de \
--to=sw@weilnetz.de \
--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).