Peter, I built in from the zipped tar ball for qemu-1.2.0 I did not get it from the repository, although I am happy to do this for you.
I used ./configure This what configure said Silently falling back into gthread backend under darwin .... C compiler gcc Host C compiler gcc Objective-C compiler clang CFLAGS -O2 -D_FORTIFY_SOURCE=2 -g QEMU_CFLAGS -m64 -DOS_OBJECT_USE_OBJC=0 -arch x86_64 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fstack-protector-all -Wendif-labels -Wmissing-include-dirs -Wempty-body -Wnested-externs -Wformat-security -Wformat-y2k -Winit-self -Wold-style-definition -I/opt/local/include/libpng15 LDFLAGS -m64 -framework CoreFoundation -framework IOKit -arch x86_64 My gcc appears to be localhost:qemu-1.2.0 oliverks$ gcc -v Using built-in specs. Target: i686-apple-darwin11 Configured with: /private/var/tmp/llvmgcc42/llvmgcc42-2336.11~28/src/configure --disable-checking --enable-werror --prefix=/Applications/Xcode.app/Contents/Developer/usr/llvm-gcc-4.2 --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-prefix=llvm- --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-slibdir=/usr/lib --build=i686-apple-darwin11 --enable-llvm=/private/var/tmp/llvmgcc42/llvmgcc42-2336.11~28/dst-llvmCore/Developer/usr/local --program-prefix=i686-apple-darwin11- --host=x86_64-apple-darwin11 --target=i686-apple-darwin11 --with-gxx-include-dir=/usr/include/c++/4.2.1 Thread model: posix gcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00) -- 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
