[Qemu-devel] [Bug 1065232] [NEW] qemu-system-arm Crashes on startup on OS X 10.8.2

[Oliver]

Public bug reported:

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

** Affects: qemu
     Importance: Undecided
         Status: New

-- 
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