From: Bob Breuer <breuerr@mc.net>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] qemu-system-sparc io-thread segfault on win32
Date: Sun, 16 Oct 2011 23:39:28 -0500 [thread overview]
Message-ID: <4E9BB180.6080506@mc.net> (raw)
I'm getting a segfault from qemu-system-sparc with the io thread enabled
on win32. This is with the latest mingw (gcc 4.6.1). mipsel also
fails, but i386 is ok. I haven't checked any of the other system
targets, but they might also show this problem.
git bisect points to commit cea5f9a cpu-exec.c: avoid AREG0 use, but
that would seem to only expose the bug instead of creating it. In
cpu_exec(), assigning any valid pointer to ebp before setjmp will get it
working again. It looks like a bogus value in ebp at the time of setjmp
will cause longjmp to abort on win32.
Here's some output from gdb for the crash:
Starting program: d:\qemu\build-mingw\sparc-softmmu\qemu-system-sparc.exe
-m 64 -L ./qemu-git/pc-bios
[New Thread 2128.0x664]
[New Thread 2128.0x5d4]
[New Thread 2128.0x6dc]
[Switching to Thread 2128.0x6dc]
Breakpoint 1, 0x00514a30 in _setjmp ()
(gdb) info registers
eax 0x1989b7c 26778492
ecx 0x1982008 26746888
edx 0x0 0
ebx 0x1982008 26746888
esp 0x378fe00 0x378fe00
ebp 0xfffffffe 0xfffffffe
esi 0x0 0
edi 0x1982008 26746888
eip 0x514a30 0x514a30 <_setjmp>
eflags 0x202 [ IF ]
cs 0x1b 27
ss 0x23 35
ds 0x23 35
es 0x23 35
fs 0x38 56
gs 0x0 0
(gdb) c
Continuing.
Program received signal SIGSEGV, Segmentation fault.
0x7800bd65 in abnormal_termination () from C:\WINNT\system32\msvcrt.dll
(gdb) bt
#0 0x7800bd65 in abnormal_termination () from
C:\WINNT\system32\msvcrt.dll
#1 0x0378ffa4 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
Bob
next reply other threads:[~2011-10-17 4:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 4:39 Bob Breuer [this message]
[not found] ` <4E9C0497.2000605@siriusit.co.uk>
2011-10-17 14:09 ` [Qemu-devel] qemu-system-sparc io-thread segfault on win32 Bob Breuer
2011-10-17 17:22 ` [Qemu-devel] gcc auto-omit-frame-pointer vs msvc longjmp Richard Henderson
2011-10-17 19:14 ` Blue Swirl
2011-10-17 20:11 ` Richard Henderson
2011-10-17 21:20 ` Bob Breuer
2011-10-17 21:31 ` Kai Tietz
2011-10-17 22:23 ` Bob Breuer
2011-10-17 22:56 ` Kai Tietz
2011-10-19 21:05 ` Bob Breuer
2011-10-19 22:19 ` Richard Henderson
2011-10-20 4:22 ` xunxun
2011-10-20 14:48 ` Kai Tietz
2011-10-20 15:34 ` Kai Tietz
[not found] ` <j7sgfi$i66$1@dough.gmane.org>
2011-10-22 5:13 ` xunxun
2011-10-22 5:21 ` xunxun
2011-10-22 11:19 ` Kai Tietz
2011-10-22 14:23 ` asmwarrior
2011-10-24 14:45 ` Bob Breuer
2011-10-24 16:18 ` Kai Tietz
2011-10-25 15:14 ` Bob Breuer
2011-10-20 13:04 ` jojelino
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=4E9BB180.6080506@mc.net \
--to=breuerr@mc.net \
--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 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.