Date: Wed, 26 Jan 2005 16:30:09 -0600 From: Dan Nelson <dnelson@allantgroup.com> To: Paul Schmehl <pauls@utdallas.edu> Cc: freebsd-questions@freebsd.org Subject: Re: Finding the source of a sigill Message-ID: <20050126223008.GE31269@dan.emsphone.com> In-Reply-To: <6ECC0AB2F09DC08A4B9BB607@utd49554.utdallas.edu> References: <8C20281367ADB834E95B5684@utd49554.utdallas.edu> <20050126163351.GC31269@dan.emsphone.com> <6ECC0AB2F09DC08A4B9BB607@utd49554.utdallas.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Jan 26), Paul Schmehl said: > --On Wednesday, January 26, 2005 10:33:51 AM -0600 Dan Nelson > <dnelson@allantgroup.com> wrote: > >In the last episode (Jan 26), Paul Schmehl said: > >>I found this in the messages log when snort died: > >> > >>Jan 26 03:19:34 buttercup2 /kernel: pid 53186 (snort), uid 0: exited on signal 4 > >> > >>There was no core dump. Is there a way to figure out what the > >>cause of the sigill was? > > > >An illegal instruction :) No way to find out any more without a > >core file. > > Any way of knowing why sigill didn't produce a core file? (It does when > make fails.) Snort might have disabled it, or it might have been disabled by a startup script. Try adding "limit -c unlimited" to the snort startup script. From the log message, it's running as root so it's not like it couldn't write the corefile. -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050126223008.GE31269>