From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D0Ki8-0001HW-Et for qemu-devel@nongnu.org; Sun, 13 Feb 2005 09:26:57 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D0Ki2-0001Fz-Sx for qemu-devel@nongnu.org; Sun, 13 Feb 2005 09:26:52 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D0Ki2-0001FA-8y for qemu-devel@nongnu.org; Sun, 13 Feb 2005 09:26:50 -0500 Received: from [212.250.162.19] (helo=mta13-winn.mailhost.ntl.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D0KSp-0000wy-WF for qemu-devel@nongnu.org; Sun, 13 Feb 2005 09:11:08 -0500 Received: from aamta05-winn.mailhost.ntl.com ([212.250.162.8]) by mta13-winn.mailhost.ntl.com with ESMTP id <20050213141107.YFYC11211.mta13-winn.mailhost.ntl.com@aamta05-winn.mailhost.ntl.com> for ; Sun, 13 Feb 2005 14:11:07 +0000 Received: from phoenix.frop.org ([80.4.6.170]) by aamta05-winn.mailhost.ntl.com with ESMTP id <20050213141107.JUVO769.aamta05-winn.mailhost.ntl.com@phoenix.frop.org> for ; Sun, 13 Feb 2005 14:11:07 +0000 From: Julian Seward Subject: Re: [Qemu-devel] KQEMU bus errors Date: Sun, 13 Feb 2005 14:10:20 +0000 References: <1108086522.5629.11.camel@localhost.localdomain> <1108287757.7619.7.camel@localhost.localdomain> <5538008c78eb9d182d41f6d73c7dbbc3@elis.ugent.be> In-Reply-To: <5538008c78eb9d182d41f6d73c7dbbc3@elis.ugent.be> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200502131410.22636.jseward@acm.org> 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 On Sunday 13 February 2005 11:13, Jonas Maebe wrote: > On 13 feb 2005, at 10:42, Darryl Dixon wrote: > > Most of the references that I can find for a Linux 'Bus error' talk > > about unaligned memory accesses. > > Indeed. The only way I know of to get a bus error under Linux/x86 from > a user space program, is to turn on the alignment check flag in the > eflags register, followed by an unaligned memory access. I have a very vague and possibly wrong memory that the another way to get a bus error is to mmap a file into an area which is too big for the file, then read/write the area beyond the end of the file. Or perhaps that was on Solaris. In any case, it might be worth checking this isn't somehow related to mmap or use of mmap. J