qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jonas Maebe <jonas.maebe@elis.ugent.be>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] KQEMU bus errors
Date: Sun, 13 Feb 2005 12:13:44 +0100	[thread overview]
Message-ID: <5538008c78eb9d182d41f6d73c7dbbc3@elis.ugent.be> (raw)
In-Reply-To: <1108287757.7619.7.camel@localhost.localdomain>


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.

Usually, this is the result from a corrupted stack, causing an invalid 
value to be restored to the eflags register (which coincidentally has 
the bit corresponding to the alignment check flag set to 1).


Jonas

  reply	other threads:[~2005-02-13 12:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-11  1:48 [Qemu-devel] KQEMU bus errors Darryl Dixon
2005-02-13  1:49 ` Julian Chesterfield
2005-02-13  2:17   ` Hetz Ben Hamo
2005-02-13  5:14     ` Brad Campbell
2005-02-13  9:42       ` Darryl Dixon
2005-02-13 11:13         ` Jonas Maebe [this message]
2005-02-13 14:10           ` Julian Seward
2005-02-13 14:51             ` Grzegorz Kulewski
2005-02-13 20:19               ` [Qemu-devel] Bus errors and /dev/shm -- was: " Darryl Dixon
2005-02-13 22:00                 ` Filip Navara
2005-02-13 12:24         ` [Qemu-devel] " Phil Krylov
2005-02-13  2:37   ` Darryl Dixon
2005-02-13  2:44   ` Grzegorz Kulewski
2005-02-21 22:24   ` [Qemu-devel] " bri3d
2005-02-21 23:04     ` Hetz Ben Hamo
2005-02-21 23:30       ` Darryl Dixon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5538008c78eb9d182d41f6d73c7dbbc3@elis.ugent.be \
    --to=jonas.maebe@elis.ugent.be \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).