[ARGUS] Segmentation Fault with 2.0.6rc2 on FreeBSD 4.9-RELEASE

[Carter Bullard]

Hey Andrew and Winfred,
   Yeah, it is/was nice to suggest that argus is that
bulletproof, but unfortunately, I believe that argus
may be the culprit this time.

Thanks for the thought though,

Carter



-----Original Message-----
From: owner-argus-info at lists.andrew.cmu.edu
[mailto:owner-argus-info at lists.andrew.cmu.edu] On Behalf Of Andrew Pollock
Sent: Thursday, April 15, 2004 11:46 PM
To: Winfred Harrelson
Cc: Argus Development Mailing list
Subject: Re: [ARGUS] Segmentation Fault with 2.0.6rc2 on FreeBSD 4.9-RELEASE

On Thu, Apr 15, 2004 at 04:15:31PM -0400, Winfred Harrelson wrote:
>
> Sorry to get to this so late (been busy lately) but I do have an idea.
> I don't know about freebsd, but when you get a signal 11 on openbsd it
> is almost always bad RAM.  Check the freebsd list archives or do a
> google search and I am sure that is what you will find.  So before
> going any further get the memtest x86 and have it run for a few hours
> to check your RAM.

I'm sorry, but I've always treated that as a fair amount of bollocks. Sure,
the RAM could be a bit dodgey, but a segmentation violation (predominantly)
means that a process tried to access some memory it shouldn't have. I don't
believe in giving massive credence to the bam RAM theory, when it can
actually be a coding problem.

http://www.google.com.au/search?q=define:Segmentation+fault+(segfault)

If the *BSD people want to push bad RAM in favour of coding errors, they're
either arrogant or just plain lazy.

Just my $0.05 worth...

Andrew