qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1065232] Re: qemu-system-arm Crashes on startup on OS X 10.8.2
Date: Wed, 10 Oct 2012 22:48:16 -0000	[thread overview]
Message-ID: <20121010224816.3790.80.malone@gac.canonical.com> (raw)
In-Reply-To: 20121010202220.32313.91692.malonedeb@soybean.canonical.com

Thanks. QEMU 1.2 (or earlier) won't work when built with a gcc which is
really an llvm-gcc, because llvm-gcc doesn't support the "tie this
variable to a specific native register" which QEMU requires. (I had
hoped it would give a compile failure, but it seems to just generate
wrong code.) We've actually been able to remove the fixed-register
requirement in QEMU's master git tree, but those changes have not yet
made it into a released version. So for now, I'm afraid you have three
choices:

 (1) compile with a real gcc (not llvm-gcc or clang)
 (2) build QEMU from git master (this is living on the "bleeding edge" but it generally works OK)
 (3) wait for 1.3

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

  parent reply	other threads:[~2012-10-10 22:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-10 20:22 [Qemu-devel] [Bug 1065232] [NEW] qemu-system-arm Crashes on startup on OS X 10.8.2 Oliver
2012-10-10 20:53 ` [Qemu-devel] [Bug 1065232] " Oliver
2012-10-10 20:57 ` Oliver
2012-10-10 21:33 ` Oliver
2012-10-10 21:45 ` Peter Maydell
2012-10-10 22:18 ` Oliver
2012-10-10 22:48 ` Peter Maydell [this message]
2012-10-10 23:21 ` Oliver
2012-10-11 12:42 ` Paolo Bonzini

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=20121010224816.3790.80.malone@gac.canonical.com \
    --to=peter.maydell@linaro.org \
    --cc=1065232@bugs.launchpad.net \
    --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).