Date: Wed, 02 Jul 1997 18:49:11 -0400 From: Mike Tancsa <mike@sentex.net> To: "Riley J. McIntire" <rileyj@train.tgci.com>, freebsd-questions@FreeBSD.ORG Subject: Re: Core dump signal 11 Message-ID: <3.0.2.32.19970702184911.00aaecd0@sentex.net> In-Reply-To: <199707022221.PAA10403@train.tgci.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 03:24 PM 7/02/97 +0000, Riley J. McIntire wrote:
>Hi,
>
>On a 2.2.2-R machine I put together a few weeks ago and walked
>away from for a while I just noticed:
>
>Jun 24 15:00:01 moat /kernal: pid 20869 (atrun), uid 0: exited on siganl
11 (core
>dumped)
>
>I know I've seen "signal 11" discussed here, but can't find it in the
>archives. My recollection is that during a "make world" a signal 11
>indicates bad memory, either ram or cache. Is that indicated here?
>Anything else?
SIG 11 could just be a poorly written program... Take for example
#include <stdio.h>
#include <time.h>
#include <sys/time.h>
void main(int argc, char **argv)
{
long inval;
inval=atol(argv[1]);
printf("%s",ctime(&inval));
}
If you run this program and do not give it an argument, it will do a sig 11
coredump. However, since the FreeBSD distribution is not poorly written,
and you start seeing SIG 11's on basic daemons and processes, I would start
looking at the hardware perhaps...
---Mike
**********************************************************************
Mike Tancsa (mike@sentex.net) * To do is to be -- Nietzsche
Sentex Communications Corp, * To be is to do -- Sartre
Cambridge, Ontario * Do be do be do -- Sinatra
(http://www.sentex.net/~mdtancsa) *
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.2.32.19970702184911.00aaecd0>