From owner-freebsd-current Thu Oct 2 06:32:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA25579 for current-outgoing; Thu, 2 Oct 1997 06:32:01 -0700 (PDT) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA25542 for ; Thu, 2 Oct 1997 06:31:56 -0700 (PDT) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id PAA04013; Thu, 2 Oct 1997 15:30:47 +0200 (CEST) To: David Langford cc: current@FreeBSD.ORG Subject: Re: problem with free() and junk pointers? In-reply-to: Your message of "Wed, 01 Oct 1997 14:44:42 -1000." <199710020044.OAA11591@caliban.dihelix.com> Date: Thu, 02 Oct 1997 15:30:47 +0200 Message-ID: <4011.875799047@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199710020044.OAA11591@caliban.dihelix.com>, David Langford writes: > >I have a three week old current box that I am trying to >get more current but I keep getting the following: > >make in free(): warning: modified (chunk-) pointer. >make in free(): warning: junk pointer, too low to make sense. >Segmentation fault - core dumped > > >This seems to be a random occurance and makes getting through a make world >a wee bit of a pain. > >Do I have a bad library or could this be a sign of bad memory? >I dont get the normal "cc died due to signal such and such" so I was >disconting the memory bit but.... It could be bad mem. The only other instance where this has been reported it was a wrong kind of refresh setup for the chips, if you can't change that in your bios (very likely), try out some other RAM sticks and see if that helps. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop."