Date: Sat, 2 Apr 2005 15:00:45 -0800 (PST) From: Doug White <dwhite@gumbysoft.com> To: Barney Wolff <barney@databus.com> Cc: freebsd-stable@freebsd.org Subject: Re: apache+mod_ssl signal 4 Message-ID: <20050402145930.G1503@carver.gumbysoft.com> In-Reply-To: <20050402065702.GA69101@pit.databus.com> References: <424D1FBD.3070207@bmby.com> <20050401185643.I94922@carver.gumbysoft.com> <20050402065702.GA69101@pit.databus.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050402145930.G1503>