From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
KVM list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Segfault starting vcpu thread
Date: Wed, 11 Jul 2012 15:08:00 +0300 [thread overview]
Message-ID: <4FFD6CA0.6050205@redhat.com> (raw)
In-Reply-To: <4FFD6BC9.7070902@redhat.com>
On 07/11/2012 03:04 PM, Avi Kivity wrote:
>>>> specific command line or guest?
>>>
>>> qemu-system-x86_64
>>
>> Just did the same, but it's all fine here.
>
> Ok, I'll debug it. Probably something stupid like a miscompile.
Indeed, a simple clean build fixed it up. Paolo, it looks like
autodependencies are still broken.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-07-11 12:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 11:46 [Qemu-devel] Segfault starting vcpu thread Avi Kivity
2012-07-11 11:55 ` Jan Kiszka
2012-07-11 11:58 ` Avi Kivity
2012-07-11 11:59 ` Jan Kiszka
2012-07-11 12:04 ` Avi Kivity
2012-07-11 12:08 ` Avi Kivity [this message]
2012-07-11 12:40 ` 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=4FFD6CA0.6050205@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--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).