From owner-freebsd-stable@FreeBSD.ORG Sat Apr 2 23:00:46 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 06E4616A4CE; Sat, 2 Apr 2005 23:00:46 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id B953643D1F; Sat, 2 Apr 2005 23:00:45 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id A9C6772DE7; Sat, 2 Apr 2005 15:00:45 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id A75E272DE5; Sat, 2 Apr 2005 15:00:45 -0800 (PST) Date: Sat, 2 Apr 2005 15:00:45 -0800 (PST) From: Doug White To: Barney Wolff In-Reply-To: <20050402065702.GA69101@pit.databus.com> Message-ID: <20050402145930.G1503@carver.gumbysoft.com> References: <424D1FBD.3070207@bmby.com> <20050401185643.I94922@carver.gumbysoft.com> <20050402065702.GA69101@pit.databus.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: ports@freebsd.org cc: Uzi Klein cc: freebsd-stable@freebsd.org Subject: Re: apache+mod_ssl signal 4 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2005 23:00:46 -0000 On Sat, 2 Apr 2005, Barney Wolff wrote: > On Fri, Apr 01, 2005 at 06:59:11PM -0800, Doug White wrote: > > > > > > pid 62364 (httpd), uid 0: exited on signal 4 (core dumped) > > > Apr 1 11:48:45 www kernel: pid 62364 (httpd), uid 0: exited on signal 4 > > > (core dumped) > > > > Signal 4 is SIGABRT, which is a software-initiated abort. > > Well, no, it's ILL, indicating perhaps code compiled for a different > cpu model than it's being run on, or a trashed library. oops. heh. I really need to get into the habit of checking signal(3) more often. Yeah, SIGILL would imply the library was improperly compiled. Since libcrypto will generate CPU-specific assembly based on the CPUTYPE setting, setting it to the wrong CPU type will cause Wierd Problems. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org