SIGSEGV is in target code:
(gdb) bt
#0 0x402fd349 in code_gen_buffer ()
#1 0x0056113b in cpu_x86_exec (env=0x19489f0)
at /usr/local/google/home/catalinp/src/qemu/cpu-exec.c:599
#2 0x005625f9 in tcg_cpu_exec (env=0x19489f0)
at
I can post the target code and the code generated by TCG - not sure
how helpful that would be. There also seems to be a diff between what
is logged by -d out_asm and what I see in gdb with disass, and the
segv occurs in one of the diff blocks.
On Fri, Nov 9, 2012 at 1:42 PM, Catalin Patulea
Hello,
I bisected down a Windows XP startup crash to the following commit:
0b57e287138728f72d88b06e69b970c5d745c44a is the first bad commit
commit 0b57e287138728f72d88b06e69b970c5d745c44a
Author: David Gibson da...@gibson.dropbear.id.au
Date: Mon Sep 10 12:30:57 2012 +1000
Reproduceable on