From: Joe Pintozzi <joseph.pintozzi@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 821289] Re: qemu mac segfault
Date: Wed, 25 Jan 2012 04:18:59 -0000 [thread overview]
Message-ID: <20120125041859.7305.30035.malone@gac.canonical.com> (raw)
In-Reply-To: 20110805061858.21259.56507.malonedeb@chaenomeles.canonical.com
Ironically I just figured out how to fix this issue. It only segfaults
when built with LLVM. If you installed with homebrew, run
>brew install qemu --use-gcc --force
To get a working version.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/821289
Title:
qemu mac segfault
Status in QEMU:
New
Bug description:
qemu-0.14.1
./configure --target-list=i386-softmmu,x86_64-softmmu,arm-softmmu
qemu(-system-(x86_64|arm))
> Segmentation fault: 11
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/821289/+subscriptions
prev parent reply other threads:[~2012-01-25 4:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 6:18 [Qemu-devel] [Bug 821289] [NEW] qemu mac segfault Stevan Vucenovic
2012-01-25 4:09 ` [Qemu-devel] [Bug 821289] " Joe Pintozzi
2012-01-25 4:18 ` Joe Pintozzi [this message]
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=20120125041859.7305.30035.malone@gac.canonical.com \
--to=joseph.pintozzi@gmail.com \
--cc=821289@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.