From owner-freebsd-current Sat Oct 3 18:52:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA07994 for freebsd-current-outgoing; Sat, 3 Oct 1998 18:52:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles144.castles.com [208.214.165.144]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA07675 for ; Sat, 3 Oct 1998 18:50:22 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA00722; Sat, 3 Oct 1998 18:55:22 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810040155.SAA00722@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: lane@dibbs.net cc: current@FreeBSD.ORG Subject: Re: VIRTUAL MEMORY EXCEEDED during make world ... In-reply-to: Your message of "Wed, 23 Sep 1998 03:56:54 -0000." <199810040058.TAA11528@dibbs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 03 Oct 1998 18:55:21 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > How do I fix that? > > This is my first time to "make world," 'cause, (I wanna be real > cautious about entering into a new world), and my 486DX churned away > for 9.75 hours on the STABLE release ... then it stopped churning and > just sat for about an hour ... (I raked the leaves in my yard while > my computer did most of the work, but I checked it periodically ... > then ... nothing ... for about 1 hour)... Then: BOOM! > > as[.c] in malloc(): warning: recursive call\n > Fatal error: virtual memory exceeded > > Is it possible to increase my swap partition ... and would this be of > any use to me in this situation? I've got about 1GIG free on /usr, > so space isn't the problem (I don't think, anyway), it just seems > that I don't have enough space allocated for swapping ... No, the "virtual memory exhausted" message is a (bad) error message from as(1). The real error is the one above it, where as(1) has attempted to call malloc() from a signal handler. It may have been trying to print an error message or something similar. Sounds like you might have run into a pathalogical overwork case. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message