From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:39049) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QatSg-0000aA-Vz for qemu-devel@nongnu.org; Sun, 26 Jun 2011 13:49:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QatSf-0006Y9-JI for qemu-devel@nongnu.org; Sun, 26 Jun 2011 13:49:34 -0400 Received: from mta-2.ms.rz.rwth-aachen.de ([134.130.7.73]:50649) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QatSf-0006Y1-7c for qemu-devel@nongnu.org; Sun, 26 Jun 2011 13:49:33 -0400 MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=ISO-8859-1; format=flowed Received: from ironport-out-1.rz.rwth-aachen.de ([134.130.5.40]) by mta-2.ms.rz.RWTH-Aachen.de (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008)) with ESMTP id <0LNE00HFDS6H4EA0@mta-2.ms.rz.RWTH-Aachen.de> for qemu-devel@nongnu.org; Sun, 26 Jun 2011 19:49:29 +0200 (CEST) Received: from [192.168.2.3] ([unknown] [84.44.132.141]) by relay-auth-1.ms.rz.rwth-aachen.de (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 9 2008)) with ESMTPA id <0LNE00AGLS6E5J00@relay-auth-1.ms.rz.rwth-aachen.de> for qemu-devel@nongnu.org; Sun, 26 Jun 2011 19:49:29 +0200 (CEST) Message-id: <4E077126.1030107@rwth-aachen.de> Date: Sun, 26 Jun 2011 19:49:26 +0200 From: "felix.matenaar@rwth-aachen" References: <4E054935.4060406@rwth-aachen.de> <4E060C98.30706@rwth-aachen.de> <4E06613D.8020603@rwth-aachen.de> In-reply-to: Subject: Re: [Qemu-devel] QEMU timing requirements List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On 06/26/2011 06:49 AM, Mulyadi Santosa wrote: > On Sun, Jun 26, 2011 at 05:29, felix.matenaar@rwth-aachen > wrote: >> Think I found the problem. It was a bug in my code and because of some weird >> circumstances, backtrace and addresses seemed to be a segfault in a BBL. > glad you find it..... care to share to everyone what's really goin' > on? who knows it will reveal somekind of hidden problem in > Qemu/TCG.... > Yes I care. But the bug was not in Qemu. It was an integer underflow caused by a race condition. The behavior of the bug just seemed to be a problem with Qemu timers but it is not. So I thought it doesn't make much sense to share a bug in my code with the list...