From owner-freebsd-stable Wed Dec 8 17:49:30 1999 Delivered-To: freebsd-stable@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id 11AC21558C for ; Wed, 8 Dec 1999 17:49:25 -0800 (PST) (envelope-from bmilekic@dsuper.net) Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id UAA30213; Wed, 8 Dec 1999 20:49:15 -0500 (EST) Date: Wed, 8 Dec 1999 20:49:15 -0500 (EST) From: Bosko Milekic To: andrew@ugh.net.au Cc: freebsd-stable@FreeBSD.ORG Subject: Re: CRON in malloc(): warning: pointer to wrong page. In-Reply-To: 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 Thu, 9 Dec 1999 andrew@ugh.net.au wrote: !>On a probably related matter we had a lot of processes die with signal 4 !>(one or two a day). We swapped the RAM and I thought it had stopped but !>one died yesterday (telnetd). Previously running make index in /usr/ports !>would always die with sig4 but since the RAM swap its been fine... !> !>Any suggestions? I assume sig4 indicates that there is corruption in !>either the memory, cache or bus but I have no idea why or what causes the !>CRON error. !> Well, are the processes dying with signal 4 dumping core? If so, have you tried debugging from the core dump? Your malloc() problem could be related to something that you discover this way. After all, the default action on receipt of signal 4 would be to dump core. --Bosko -- Bosko Milekic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message