From: "support" <support@richardlinux.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Segmentation Fault
Date: Wed, 26 Jan 2005 08:01:14 [thread overview]
Message-ID: <20050126080114.3621.qmail@server287.com> (raw)
Good people,
I lost count trying to install Windows XP with Qemu without success. I am working with Fedora Core 3 and tried qemu and winxp using the official FC3 Kernel (2.6.10-1.741_FC3), cusomised Kernel (2.6.10-ck5), gcc-3.4.2, gcc-3.4.3, with ready made FC3 0.6.1 rpm package, and with the latest snapshot (2005-01-24) (./configure --prefix=/usr, make, make install). The problem is a nusty segmentation fault. Considering Windows XP takes a few hours to reach this point you can understand my frustration (it always happens at approximately the same stage of the winxp installation).
Here is a gdb dump -
Program received signal SIGSEGV, Segmentation fault.
0x0884ae8c in code_gen_buffer ()
(gdb) bt
#0 0x0884ae8c in code_gen_buffer ()
#1 0x08092039 in cpu_x86_exec (env1=0x9b96958)
at /home/systema/qemu/cpu-exec.c:543
#2 0x0804d0bf in main_loop () at /home/systema/qemu/vl.c:2679
#3 0x0804e307 in main (argc=0, argv=0xffdff000)
at /home/systema/qemu/vl.c:3675
(gdb) bt full
#0 0x0884ae8c in code_gen_buffer ()
No symbol table info available.
#1 0x08092039 in cpu_x86_exec (env1=0x9b96958)
at /home/systema/qemu/cpu-exec.c:543
ptb = (TranslationBlock **) 0x9b97474
tb = (TranslationBlock *) 0x811ad020
saved_T0 = 163146072
saved_T1 = 0
saved_T2 = 0
saved_env = (CPUX86State *) 0xbff5b248
code_gen_size = 0
ret = 256
interrupt_request = 0
tb = (TranslationBlock *) 0x833cc64
ptb = (TranslationBlock **) 0x82e022c
cs_base = 0
pc = 2152578619
tc_ptr = (
unsigned char *) 0x811ad020 <Address 0x811ad020 out of bounds>
flags = 2740
#2 0x0804d0bf in main_loop () at /home/systema/qemu/vl.c:2679
ret = -2128949216
timeout = 163148916
env = (CPUX86State *) 0x7589f029
#3 0x0804e307 in main (argc=0, argv=0xffdff000)
at /home/systema/qemu/vl.c:3675
p = 0x1010101 <Address 0x1010101 out of bounds>
fd = 163148916
use_gdbstub = 16843009
gdbstub_port = 16843009
i = 6
has_cdrom = 16843009
snapshot = 16843009
env = (CPUX86State *) 0x6
initrd_filename = 0x1010101 <Address 0x1010101 out of bounds>
hd_filename = {0x0, 0x0, 0x0, 0x0}
fd_filename = {0x1010101 <Address 0x1010101 out of bounds>,
0x1010101 <Address 0x1010101 out of bounds>}
kernel_filename = 0x1010101 <Address 0x1010101 out of bounds>
kernel_cmdline = 0x1010101 <Address 0x1010101 out of bounds>
cyls = 16843009
heads = 16843009
secs = 16843009
translation = 16843009
start_emulation = 16843009
macaddr = "\000\000\000\000\000"
net_if_type = 16843009
nb_tun_fds = 16843009
tun_fds = {0, 0, 0, 0, 0, 0, 0, 0}
optind = 16843009
r = 0xffdff128 <Address 0xffdff128 out of bounds>
optarg = 0x0
monitor_hd = (CharDriverState *) 0x9b97474
monitor_device = '\0' <repeats 127 times>
serial_devices = {'\0' <repeats 127 times>, '\0' <repeats 127 times>,
'\0' <repeats 127 times>, '\0' <repeats 127 times>}
serial_device_index = 16843009
parallel_devices = {'\0' <repeats 127 times>,
'\0' <repeats 127 times>, '\0' <repeats 127 times>}
parallel_device_index = 16843009
loadvm = 0x1010101 <Address 0x1010101 out of bounds>
(gdb)
Any help appreciated.
next reply other threads:[~2005-01-26 8:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 8:01 support [this message]
2005-01-26 9:15 ` [Qemu-devel] Segmentation Fault zitu
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=20050126080114.3621.qmail@server287.com \
--to=support@richardlinux.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).