From: Adam Lackorzynski <adam@os.inf.tu-dresden.de>
To: qemu-devel@nongnu.org
Cc: Julien Grall <julien.grall@citrix.com>
Subject: [Qemu-devel] Qemu x86 segfault
Date: Fri, 4 Jan 2013 11:13:49 +0100 [thread overview]
Message-ID: <20130104101349.GD6916@os.inf.tu-dresden.de> (raw)
Hi,
I'm seeing the following segfault of qemu-system-i386 and
qemu-system-x86_64 with master. git bisect points to
258711c6448c44b60b0fecef1d3b09c71e23e304.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xea930b70 (LWP 14297)]
0x00000000 in ?? ()
(gdb) bt
#0 0x00000000 in ?? ()
#1 0x567a1b48 in memory_region_read_accessor (opaque=opaque@entry=0x5704ab58,
addr=0, value=value@entry=0xea92fe10, size=size@entry=1, shift=0, mask=255)
at qemu/memory.c:316
#2 0x567a1536 in access_with_adjusted_size (addr=<optimized out>,
value=value@entry=0xea92fe10, size=size@entry=1,
access_size_min=<optimized out>, access_size_max=<optimized out>,
access=access@entry=0x567a1ac0 <memory_region_read_accessor>,
opaque=opaque@entry=0x5704ab58) at qemu/memory.c:364
#3 0x567a288b in memory_region_iorange_read (iorange=0x57098fd0, offset=0,
width=1, data=0xea92fe10) at qemu/memory.c:409
#4 0x5679bc4f in ioport_readb_thunk (opaque=0x57098fd0, addr=128)
at qemu/ioport.c:186
#5 0x5679c8a5 in ioport_read (address=128, index=0)
at qemu/ioport.c:70
#6 cpu_inb (addr=addr@entry=128) at qemu/ioport.c:309
#7 0x567e0637 in helper_inb (port=128)
at qemu/target-i386/misc_helper.c:77
#8 0xeee28e84 in code_gen_buffer ()
#9 0x5673e528 in cpu_x86_exec (env=env@entry=0x570077c8)
at qemu/cpu-exec.c:599
#10 0x5674043b in tcg_cpu_exec (env=0x570077c8)
at qemu/cpus.c:1115
#11 tcg_exec_all () at qemu/cpus.c:1148
#12 qemu_tcg_cpu_thread_fn (arg=0x57007788)
at qemu/cpus.c:841
#13 0xf79d0c39 in start_thread (arg=0xea930b70) at pthread_create.c:304
#14 0xf793d78e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130
(gdb)
With ioport logging enabled, the last few lines of qemu.log are:
inb : 03fd 60
outb: 03f9 00
inb : 03f9 00
outb: 03f9 00
inb : 03fd 60
outb: 03f8 34
inb : 03fd 60
outb: 03f9 00
inb : 03f9 00
outb: 03f9 00
inb : 03fd 60
outb: 03f8 0d
inb : 03fd 60
outb: 03f9 00
inb : 03f9 00
outb: 03f9 00
inb : 03fd 60
outb: 03f8 0a
inb : 03fd 60
outb: 03f9 00
inb : 03f9 00
outb: 03f9 00
In memory_region_read_accessor(), the function pointer mr->ops->read is
nil. Please let me know if any more info is required.
Adam
--
Adam adam@os.inf.tu-dresden.de
Lackorzynski http://os.inf.tu-dresden.de/~adam/
reply other threads:[~2013-01-04 10:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130104101349.GD6916@os.inf.tu-dresden.de \
--to=adam@os.inf.tu-dresden.de \
--cc=julien.grall@citrix.com \
--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).