From owner-freebsd-security Mon May 21 19:57:52 2001 Delivered-To: freebsd-security@freebsd.org Received: from fritz.cc.gt.atl.ga.us (fritz.cc.gt.atl.ga.us [199.77.128.120]) by hub.freebsd.org (Postfix) with ESMTP id ECFE037B446 for ; Mon, 21 May 2001 19:57:49 -0700 (PDT) (envelope-from dagon@fritz.cc.gt.atl.ga.us) Received: (from dagon@localhost) by fritz.cc.gt.atl.ga.us (8.9.3/8.9.3) id XAA20983; Mon, 21 May 2001 23:28:54 -0400 (EDT) (envelope-from dagon) Date: Mon, 21 May 2001 23:28:53 -0400 From: David Dagon To: Michael Tang Helmeste Cc: freebsd-security@FreeBSD.ORG Subject: Re: Qmail + FreeBSD 4.3 Message-ID: <20010521232853.A20683@fritz.cc.gt.atl.ga.us> References: <200105220116.IAA11516@banyan.cs.ait.ac.th> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from glassfish@frogbox.dyndns.org on Mon, May 21, 2001 at 09:35:52PM -0400 X-Echelon: RSA Crypto C4 Mossad CIA BXA Export Control Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, May 21, 2001 at 09:35:52PM -0400, Michael Tang Helmeste wrote: > actually it just means segmentation fault > > it happens when a program accesses some memory that it doesn't own Yep; it could be a bug OR hardware. The FAQ has more on this, along with suggestions: http://www.freebsd.org/doc/en_US.ISO_8859-1/books/faq/troubleshoot.html http://www.bitwizard.nl/sig11/ -- David Dagon dagon@cc.gatech.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message