From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MbZsu-0006nr-Ac
	for qemu-devel@nongnu.org; Thu, 13 Aug 2009 08:58:24 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MbZsn-0006mW-HE
	for qemu-devel@nongnu.org; Thu, 13 Aug 2009 08:58:22 -0400
Received: from [199.232.76.173] (port=44957 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MbZsm-0006mJ-KB
	for qemu-devel@nongnu.org; Thu, 13 Aug 2009 08:58:16 -0400
Received: from mx2.redhat.com ([66.187.237.31]:53263)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <avi@redhat.com>) id 1MbZsm-00078j-5Y
	for qemu-devel@nongnu.org; Thu, 13 Aug 2009 08:58:16 -0400
Message-ID: <4A840DE0.2060202@redhat.com>
Date: Thu, 13 Aug 2009 15:58:08 +0300
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
References: <20090812150159.GW5348@arachsys.com> <4A82E200.3040107@redhat.com>
	<20090812162401.GB8115@arachsys.com>
	<20090813122333.GA2863@arachsys.com> <4A840A3E.1040400@redhat.com>
	<20090813124350.GA21678@arachsys.com>
	<20090813124546.GB21678@arachsys.com>
In-Reply-To: <20090813124546.GB21678@arachsys.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Re: qemu-kvm segfaults in qemu_del_timer (0.10.5 and
	0.10.6)
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Chris Webb <chris@arachsys.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org

On 08/13/2009 03:45 PM, Chris Webb wrote:
> Chris Webb<chris@arachsys.com>  writes:
>
>    
>> Avi Kivity<avi@redhat.com>  writes:
>>
>>      
>>> csock looks corrupted, should be -1 or an fd.  Was a vnc client connected?
>>> Was the guest playing with the display resolution?
>>>        
>> Yes, I think in this case there was a vncviewer connected, and the guest had
>> started booting up into windows, which changes the resolution a couple of
>> times.
>>      
>
> Also, I think the vncviewer might actually have been disconnecting at about
> the time the segfault happened.
>
>    

master branch has a patch that fixes a use-after-free when 
disconnecting.  Unfortunately it doesn't port cleanly to stable-0.10.

-- 
error compiling committee.c: too many arguments to function