From: Mario Goppold <mgoppold@tbz-pariv.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] 32bit emulation in x86_64 System emulation
Date: Thu, 27 Oct 2005 08:37:04 +0200 [thread overview]
Message-ID: <200510270837.04842.mgoppold@tbz-pariv.de> (raw)
Hi list,
I've tried to install SuSE92 x68_64 as guest (qemu 0.7.2 with and without
kqemu). During the install grub terminates with core. But not only grub
terminates:
#include <stdio.h>
int main() {
printf("Hallo Welt!\n");
return 0;
}
gcc a.c ; ./a.out is ok but
gcc -m32 a.c; ./a.out Segmentation fault (core dumped)
with gdb:
Core was generated by `./a.out'.
Program terminated with signal 11, Segmentation fault.
warning: current_sos: Can't read pathname for load map: Input/output error
Reading symbols from /lib/tls/libc.so.6...done.
Loaded symbols for /lib/tls/libc.so.6
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
#0 0x5568aff4 in ?? () from /lib/tls/libc.so.6
(gdb) where
#0 0x5568aff4 in ?? () from /lib/tls/libc.so.6
#1 0x555d4bf3 in _IO_file_stat_internal () from /lib/tls/libc.so.6
#2 0x555d4bf3 in _IO_file_stat_internal () from /lib/tls/libc.so.6
#3 0x555ca494 in _IO_file_doallocate_internal () from /lib/tls/libc.so.6
#4 0x555d77be in _IO_doallocbuf_internal () from /lib/tls/libc.so.6
#5 0x555d550a in _IO_new_file_overflow () from /lib/tls/libc.so.6
#6 0x555d49fd in _IO_new_file_xsputn () from /lib/tls/libc.so.6
#7 0x555b25e8 in vfprintf () from /lib/tls/libc.so.6
#8 0x555ba7b0 in printf () from /lib/tls/libc.so.6
#9 0x080483e0 in main () at a.c:4
What's worng? Outside of qemu it works fine.
In the meantime i've found out that's not (only) a SuSE problem:
SuSE92, SuSE93, SuSE10, FC4 fails but Ubuntu 5.10 works fine (all in x86_64).
Have anyone see this behaviour. What can i do?
Mario
next reply other threads:[~2005-10-27 6:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 6:37 Mario Goppold [this message]
2005-10-28 10:46 ` [Qemu-devel] 32bit emulation in x86_64 System emulation Mario Goppold
2005-11-11 14:00 ` [SOLVED] " Mario Goppold
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=200510270837.04842.mgoppold@tbz-pariv.de \
--to=mgoppold@tbz-pariv.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).