Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!uunet!ogicse!usenet.coe.montana.edu!nate From: nate@cs.montana.edu (Nate Williams) Newsgroups: comp.os.386bsd.bugs Subject: Re: Out of memory? Message-ID: <1993Mar25.162406.23895@coe.montana.edu> Date: 25 Mar 93 16:24:06 GMT Article-I.D.: coe.1993Mar25.162406.23895 References: <crt.732897369@tiamat.umd.umich.edu> <summer.732933611@mullian.ee.Mu.OZ.AU> <C4Ep1x.F56@ns1.nodak.edu> <2069@hcshh.hcs.de> Sender: usenet@coe.montana.edu (USENET News System) Organization: CS Lines: 24 In article <2069@hcshh.hcs.de> hm@hcshh.hcs.de (Hellmuth Michaelis) writes: > >>I have a Gateway2000 EISA system with 16 megs ram, 32 megs swap, and >>could not process the documentation for gnu emacs without an "Out of >>Memory" error. :-( > >This has nothing to to with swap-space, i had similar problems a while ago, >and got some mail from James Clark: > >The problem is caused by a bug in g++ 1.39: operator delete (the C++ >equivalent of free()) doesn't work properly. > >Apply the following fix to g++ or upgrade to a newer version: Fixed since patchkit-0.2. You have to re-compile g++, and then re-compile groff for this patch to work. Nate -- osynw@terra.oscs.montana.edu | Still trying to find a good reason for nate@cs.montana.edu | these 'computer' things. Personally, work #: (406) 994-4836 | I don't think they'll catch on - home #: (406) 586-0579 | Don Hammerstrom