** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1361912
Title:
qemu-mips64 Segmentation fault
Status in QEMU:
Fix Released
Bug
I've just checked with current head-of-git QEMU and we can execute the
attached mips executable OK, so we've clearly fixed this bug at some
point in the last three years. Closing as fix-committed, since the fix
will definitely be in 2.11, though it's quite likely that 2.10 would
also work.
**
Could you please provide backtrace and give more details to reproduce
the issue?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1361912
Title:
qemu-mips64 Segmentation fault
Status in QEMU:
New
This is a error in user mode, I think it should be very easy to
reproduce.
On Thu, Sep 11, 2014 at 4:55 AM, Leon Alrae leon.al...@imgtec.com
wrote:
Could you please provide backtrace and give more details to reproduce
the issue?
--
You received this bug notification because you are
I forgot to add that qemu-mips64 works for me, that's why I asked for
the details to reproduce the issue (i.e. what is lang, what tools you
used to build it, command line etc.)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
I can see the problem with any simple program:
1. cat t.c
#include stdio.h
int main()
{
printf(Hello QEMU.\n);
}
2. mips64-gcc -static t.c -o t
3. qemu-mips64 t
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault (core dumped)
I built QEMU on Ubuntu 12.04 with
