From: Stefan Weil <sw@weilnetz.de>
To: Brendan Kirby <bkirby@mips.com>
Cc: Riku Voipio <riku.voipio@iki.fi>,
qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [target-mips] qemu on centos
Date: Sat, 24 Dec 2011 00:27:04 +0100 [thread overview]
Message-ID: <4EF50E48.1060805@weilnetz.de> (raw)
In-Reply-To: <4EF5076F.1070603@weilnetz.de>
Am 23.12.2011 23:57, schrieb Stefan Weil:
> Am 23.12.2011 19:05, schrieb Brendan Kirby:
>> Attached are three MIPS binaries that I have seen segfault
>> intermittently on CentOS 6 machines. Just run them with no arguments
>> several times.
>>
>> Brendan
>>
> I tried your binaries with latest QEMU. All three fail here each time
> with SIGSEGV. This is caused by a jump to address 0 (pc = 0).
> Up to now I don't know the reason for this jump.
[snip]
> An older qemu-mipsel from August fails, too.
>
> Regards,
> Stefan Weil
A version from May is better: it also has a jump to address 0,
but handles it correctly:
qemu-mipsel -L /media/vm/tftpboot/mips/malta-le mipsbin/bisort.llc.mips32r2
qemu: unhandled CPU exception 0xc - aborting
pc=0x00000000 HI=0x0000018a LO=0x0000f816 ds 0022 00000000 0
GPR00: r0 00000000 at fffffff8 v0 4081190c v1 00000814
GPR04: a0 0040107c a1 00000001 a2 4080043c a3 004012a0
GPR08: t0 00401344 t1 0ffffffe t2 00000063 t3 00000002
GPR12: t4 40800190 t5 40800238 t6 ffffffff t7 004006a8
GPR16: s0 4083a010 s1 00400660 s2 00000000 s3 00000000
GPR20: s4 00000000 s5 00000000 s6 00000000 s7 00000000
GPR24: t8 00000000 t9 00000000 k0 00000000 k1 00000000
GPR28: gp 00411544 sp 40800418 s8 00000000 ra 00401520
CP0 Status 0x00000000 Cause 0x00000000 EPC 0x00000000
Config0 0x80000482 Config1 0x9e190c8f LLAddr 0xffffffff
CP1 FCR0 0x00000000 FCR31 0x00000000 SR.FR 0 fp_status 0x00
f0: w:3f800000 d:400000003f800000 fd: 4.61169e+18 fs: 1.06535e+09
psu: 1.07374e+09
f2: w:00000000 d:0000000000000000 fd: 0 fs: 0
psu: 0
f4: w:00000000 d:0000000000000000 fd: 0 fs: 0
psu: 0
f6: w:00000000 d:0000000000000000 fd: 0 fs: 0
psu: 0
f8: w:00000000 d:0000000000000000 fd: 0 fs: 0
psu: 0
f10: w:00000000 d:0000000000000000 fd: 0 fs: 0
psu: 0
f12: w:00000000 d:0000000000000000 fd: 0 fs: 0
psu: 0
f14: w:00000000 d:0000000000000000 fd: 0 fs: 0
psu: 0
f16: w:00000000 d:0000000000000000 fd: 0 fs: 0
psu: 0
f18: w:00000000 d:0000000000000000 fd: 0 fs: 0
psu: 0
f20: w:00000000 d:0000000000000000 fd: 0 fs: 0
psu: 0
f22: w:00000000 d:0000000000000000 fd: 0 fs: 0
psu: 0
f24: w:00000000 d:0000000000000000 fd: 0 fs: 0
psu: 0
f26: w:00000000 d:0000000000000000 fd: 0 fs: 0
psu: 0
f28: w:00000000 d:0000000000000000 fd: 0 fs: 0
psu: 0
f30: w:00000000 d:0000000000000000 fd: 0 fs: 0
psu: 0
qemu: uncaught target signal 6 (Aborted) - core dumped
Obviously signal handling for SIGSEGV in user code changed.
It now raises a SIGSEGV on the host...
Merry Christmas
Stefan Weil
next prev parent reply other threads:[~2011-12-23 23:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4EF4B3C0.8030204@mips.com>
2011-12-23 18:05 ` [Qemu-devel] Fwd: Re: [target-mips] qemu on centos Brendan Kirby
2011-12-23 22:57 ` Stefan Weil
2011-12-23 23:21 ` Brendan Kirby
2011-12-23 23:27 ` Stefan Weil [this message]
2012-01-16 21:38 ` Andreas Färber
2011-12-23 12:44 [Qemu-devel] " Reed Kotler
2011-12-23 13:25 ` [Qemu-devel] [target-mips] " Andreas Färber
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=4EF50E48.1060805@weilnetz.de \
--to=sw@weilnetz.de \
--cc=aurelien@aurel32.net \
--cc=bkirby@mips.com \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.