From owner-freebsd-questions@FreeBSD.ORG Tue Mar 22 16:22:34 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D8CC916A4CE for ; Tue, 22 Mar 2005 16:22:34 +0000 (GMT) Received: from fusion.vilot.net (vilot.com [64.246.32.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E4E243D5D for ; Tue, 22 Mar 2005 16:22:34 +0000 (GMT) (envelope-from tom@vilot.com) Received: from vilot.com (c-24-8-184-241.client.comcast.net [24.8.184.241]) (authenticated bits=0) by fusion.vilot.net (8.13.1/8.12.9) with ESMTP id j2MGMX73071046 for ; Tue, 22 Mar 2005 10:22:33 -0600 (CST) (envelope-from tom@vilot.com) Received: by vilot.com (sSMTP sendmail emulation); Tue, 22 Mar 2005 09:22:16 -0700 From: "Tom Vilot" Date: Tue, 22 Mar 2005 09:22:16 -0700 To: freebsd-questions@freebsd.org Message-ID: <20050322162216.GA1354@vilot.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Organization: 3Dimentia, Inc. Mailer: mutt for FreeBSD Subject: PHP / Apache bus error X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Mar 2005 16:22:35 -0000 I've done a lot of snooping around Google to figure this out. I've come to the conclusion that PHP just plain sucks ;c) I am fairly consistently getting bus errors in Apache when I use PHP (or at least, I'm fairly sure it is due to PHP). Entries like: ... [notice] child pid 70121 exit signal Segmentation fault (11) Or if I run Apache in stand-alone mode, I will often simply get: Bus Error and it exits immediately. I am running php4-4.3.10_2 and apache+mod_ssl-1.3.33+2.8.22 on FreeBSD 4.9 RELEASE (Generic kernel). Is this something that will clear up if I move to FreeBSD 5.3? Or is there some other known work-around? I ask because I have a 5.3 box here at home that does not seem to be exhibiting this behavior. Thanks.