From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:45491) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Soven-0005vT-Eh for qemu-devel@nongnu.org; Wed, 11 Jul 2012 08:04:43 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Sovef-000644-6L for qemu-devel@nongnu.org; Wed, 11 Jul 2012 08:04:37 -0400 Received: from mx1.redhat.com ([209.132.183.28]:61162) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Sovee-00063v-UY for qemu-devel@nongnu.org; Wed, 11 Jul 2012 08:04:29 -0400 Message-ID: <4FFD6BC9.7070902@redhat.com> Date: Wed, 11 Jul 2012 15:04:25 +0300 From: Avi Kivity MIME-Version: 1.0 References: <4FFD67B2.5090306@redhat.com> <4FFD69A9.2050504@siemens.com> <4FFD6A5C.4060808@redhat.com> <4FFD6AB9.7010000@siemens.com> In-Reply-To: <4FFD6AB9.7010000@siemens.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Segfault starting vcpu thread List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: qemu-devel , KVM list On 07/11/2012 02:59 PM, Jan Kiszka wrote: >>> >>> I will try to reproduce. Is there a tree of the merge available? >> >> I just merged upstream into qemu-kvm master. For some reason there were >> no conflicts. > > A rare moment, I guess. ;) I'll put it down to random chance until we can figure out who's responsible. > >> >>> Any >>> 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. -- error compiling committee.c: too many arguments to function