From: Thayne Harbaugh <thayne@c2.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Insta-segfault! i386-linux-user
Date: Tue, 18 Sep 2007 06:32:03 -0600 [thread overview]
Message-ID: <1190118724.9564.49.camel@phantasm.home.enterpriseandprosperity.com> (raw)
Has anyone seen an insta-segfault with i386-linux-user qemu? I've
compiled qemu-0.9.0 as well as qemu-cvs (2007-09-18) with gcc-3.4 and
-fno-strict-aliasing on an amd64 and I get this:
./i386-linux-user/qemu-i386 --help
Segmentation fault
>From GDB:
Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
(gdb) bt
#0 0x0000000000000000 in ?? ()
#1 0x00000000600575ed in __libc_csu_init ()
#2 0x00002b826c660ade in __libc_start_main () from /lib/libc.so.6
#3 0x00000000600050e9 in _start ()
Nice NULL frame there - and it's before main() is reached.
Install prefix /usr
BIOS directory /usr/share/qemu
binary directory /usr/bin
Manual directory /usr/share/man
ELF interp prefix /usr/gnemul/qemu-%M
Source path /home/thayne/dev/c2/qemu-0.9.0
C compiler gcc-3.4
Host C compiler gcc (also tried with gcc-3.4)
make make
install install
host CPU x86_64
host big endian no
target list i386-linux-user arm-linux-user
gprof enabled no
profiler no
static build no
SDL support yes
SDL static link yes
mingw32 support no
Adlib support yes
CoreAudio support no
ALSA support yes
DSound support no
FMOD support no
kqemu support yes
Documentation yes
CFLAGS -Wall -fno-strict-aliasing -Wall -ggdb -fno-strict-aliasing
libc 2.6.1-1 (debian lenny)
next reply other threads:[~2007-09-18 12:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 12:32 Thayne Harbaugh [this message]
2007-09-18 13:53 ` [Qemu-devel] Insta-segfault! i386-linux-user Ronald
2007-09-18 18:25 ` Thayne Harbaugh
2007-09-18 19:11 ` Alexander Graf
2007-09-18 21:49 ` Thayne Harbaugh
2007-09-18 22:07 ` Alexander Graf
2007-09-18 22:41 ` J. Mayer
2007-09-18 22:57 ` Alexander Graf
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=1190118724.9564.49.camel@phantasm.home.enterpriseandprosperity.com \
--to=thayne@c2.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 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).