Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!uunet!pipex!bnr.co.uk!demon!centrix.demon.co.uk!damian Newsgroups: comp.os.386bsd.questions From: damian@centrix.demon.co.uk (damian) Subject: gcc eating up my machine Distribution: world Organization: Centrix Date: Mon, 12 Apr 1993 07:54:37 +0000 Message-ID: <9304120856.aa13605@gate.demon.co.uk> Sender: usenet@demon.co.uk Lines: 32 This is really two problems: 1) When compiling /usr/src/usr.bin/g++/cc1plus/cplus-parse.y it gets through yacc ok, but when cc (gcc) compiles it gets into some sort of loop and never makes it through (I left my m/c overnight to make sure). Trouble is it has munched so much memory or cpu that if it is not a foreground task I can't get any cpu time to kill it. The disk light is still plinking though not on all the time. I have had this problem before when compiling up a bit of X source that contained a large initialised static string (it was a bit image for a logo). I presume it is happening here because the yacc output has some large initialised static arrays for it's state tables. Any ideas as to why this should be happening? 2) Should the OS allow a process to hog all the available CPU & memory such that there is nothing left to get in and do anything about it? My H/W & OS:- 386/33 with 387 8M memory 300M HD 386BSD 0.1 patch 0.2.2 (just installed, doing buildworld.sh!) Thanks Damian -- +----------------------------+------------------------------------------------+ | Damian Ivereigh | If you can't suss out what this is replying to | | damian@centrix.demon.co.uk | get a threaded news reader, like trn. :-) | | Twickenham, U.K. | This is the best way to cut wasted traffic | +----------------------------+------------------------------------------------+