From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BsU1z-0007zt-OM for qemu-devel@nongnu.org; Wed, 04 Aug 2004 18:14:43 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BsU1y-0007za-SY for qemu-devel@nongnu.org; Wed, 04 Aug 2004 18:14:43 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BsU1y-0007zJ-Oz for qemu-devel@nongnu.org; Wed, 04 Aug 2004 18:14:42 -0400 Received: from [80.91.224.249] (helo=main.gmane.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BsTy4-0005T9-Pc for qemu-devel@nongnu.org; Wed, 04 Aug 2004 18:10:40 -0400 Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1BsTy3-0005cN-00 for ; Thu, 05 Aug 2004 00:10:39 +0200 Received: from vserver.cs.uit.no ([129.242.16.151]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 05 Aug 2004 00:10:39 +0200 Received: from frodef by vserver.cs.uit.no with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 05 Aug 2004 00:10:39 +0200 From: Frode Vatvedt Fjeld Date: Thu, 05 Aug 2004 00:10:34 +0200 Message-ID: <2hpt66pnad.fsf@vserver.cs.uit.no> References: <2h4qnuevha.fsf@vserver.cs.uit.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: news Subject: [Qemu-devel] Re: Bug in emulation of 'bound' x86 instruction? Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Frode Vatvedt Fjeld writes: > I'm suspecting that there's a bug in Qemu's emulation of the x86 > 'bound' instruction. The effect of this bug seems to be to add 1 to > the ESP register, which of course havocs everything. [..] Well, the response to this report has been nothing, but I'd really like to see it fixed so that I'll be able to use qemu, which otherwise seems to be really great. Also, it seems to me that if my report is correct then this bug is quite serious, and can affect a lot of software in unpredictable ways. I don't think I'll be able to submit a patch for it myself, but if I can somehow assist someone "in the know" with anything, please let me know. Regards, -- Frode Vatvedt Fjeld