From owner-freebsd-hackers  Sun Feb  9 22:54:32 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id WAA13571
          for hackers-outgoing; Sun, 9 Feb 1997 22:54:32 -0800 (PST)
Received: from www.trifecta.com (www.trifecta.com [206.245.150.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA13559
          for <freebsd-hackers@freebsd.org>; Sun, 9 Feb 1997 22:54:24 -0800 (PST)
Received: (from dev@localhost) by www.trifecta.com (8.7.5/8.6.12) id BAA04771; Mon, 10 Feb 1997 01:55:29 -0500 (EST)
Date: Mon, 10 Feb 1997 01:55:29 -0500 (EST)
From: Dev Chanchani <dev@trifecta.com>
To: Charles Mott <cmott@srv.net>
cc: freebsd-hackers@freebsd.org
Subject: Re: Bus Errors
In-Reply-To: <Pine.BSF.3.91.970209174624.3664A-100000@darkstar>
Message-ID: <Pine.BSF.3.91.970210015430.4759A-100000@www.trifecta.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

You will usually get segmentation faults when you try to reference memory 
you are not allowed to (eg. trying to follow a pointer with an invalid 
address).

The bus error usually occurs when you try to return from a function to an 
invalid address (usually meaing you clobbered your saved stack pointer)..



On Sun, 9 Feb 1997, Charles Mott wrote:

> What does "Bus error" mean?
>