One more comment, the env address looks wrong going all the way up the stack
#0 0x0000000100436b71 in gen_intermediate_code_internal (env=0x102064680, tb=0x108e5b070, search_pc=1) at translate.c:9793 #1 0x0000000100437776 in gen_intermediate_code_pc (env=0x102064680, tb=0x108e5b070) at translate.c:9961 #2 0x000000010044539f in cpu_restore_state (tb=0x108e5b070, env=0x102064680, searched_pc=4410683708) at translate-all.c:126 #3 0x00000001003ed7b3 in tlb_fill (env1=0x102064680, addr=17328, is_write=0, mmu_idx=0, retaddr=4410683708) at op_helper.c:93 #4 0x00000001003ec14d in __ldl_mmu (addr=17328, mmu_idx=0) at softmmu_template.h:159 #5 0x0000000106e5b13d in ?? () Olvier -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1065232 Title: qemu-system-arm Crashes on startup on OS X 10.8.2 Status in QEMU: New Bug description: On startup qemu-system-arm crashes on this line 9373 of target-arm if (unlikely(!QTAILQ_EMPTY(&env->breakpoints))) { QTAILQ_FOREACH(bp, &env->breakpoints, entry) { if (bp->pc == dc->pc) { // <-- CRASH !!!! gen_exception_insn(dc, 0, EXCP_DEBUG); /* Advance PC so that clearing the breakpoint will invalidate this TB. */ dc->pc += 2; goto done_generating; break; } } What appears to be happening is env is (gdb) print env->breakpoints $4 = { tqh_first = 0x1f001f001f001f, tqh_last = 0x1f001f001f001f } which leads to bp being set to (gdb) print bp $1 = (CPUBreakpoint *) 0x1f001f001f001f This looks like a bad address and causes the following statement Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: 13 at address: 0x0000000000000000 I am wondering if the env structure is not getting setup correctly? I am running the 1.2.0 version of qemu on Darwin localhost 12.2.0 Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64 x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1065232/+subscriptions