From owner-freebsd-stable Tue Jun 15 16:56:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from debonair.pussycatwatch.com (debonair.pussycatwatch.com [206.251.95.62]) by hub.freebsd.org (Postfix) with ESMTP id 0331214BF6 for ; Tue, 15 Jun 1999 16:56:23 -0700 (PDT) (envelope-from rich@paranoid.org) Received: by debonair.pussycatwatch.com (Postfix, from userid 500) id 8EDBB46813; Tue, 15 Jun 1999 17:02:38 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by debonair.pussycatwatch.com (Postfix) with ESMTP id 78A3CC02A for ; Tue, 15 Jun 1999 17:02:38 -0700 (PDT) Date: Tue, 15 Jun 1999 17:02:38 -0700 (PDT) From: Rich Burroughs X-Sender: rich@debonair.pussycatwatch.com To: freebsd-stable@freebsd.org Subject: Re: signal 6 In-Reply-To: <19990615223150.A13326@walton.maths.tcd.ie> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 15 Jun 1999, David Malone wrote: > Check for /etc/malloc.conf and the environment variable MALLOC_OPTIONS, > I know the "X" flag for malloc makes ld core dump. Ok. I'll check there. I think it is a memory issue, though. We slapped a little bit more of physical RAM into the box and now I make it quite a bit further into the kernel compile before I get the signal 6. I guess it's freaking out when it's low on physical memory. I'm not sure why, when there's a bunch of swap just begging to get used. The last time I tried, it was using 0 swap again. I'm going to add even more RAM in a couple of days, so we'll see what happens... Thanks for all of the suggestions. Rich To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message