Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA1886 ; Tue, 23 Feb 93 15:02:38 EST Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!uunet!mcsun!sunic!isgate!krafla!adamd From: adamd@rhi.hi.is (Adam David) Newsgroups: comp.os.386bsd.questions Subject: Re: SIGSEGV while linking kernel (???) Message-ID: <6388@krafla.rhi.hi.is> Date: 22 Feb 93 11:27:28 GMT References: <6383@krafla.rhi.hi.is> <CGD.93Feb21173057@gaia.CS.Berkeley.EDU> Sender: usenet@rhi.hi.is Lines: 15 Nntp-Posting-Host: hengill.rhi.hi.is cgd@gaia.CS.Berkeley.EDU (Chris G. Demetriou) writes: >this has happened to me occasionally, generally after my machine >crashed while making some kernel object files... This was in fact the case, I had already removed 2 zero-length files. It turned out that another object file was corrupted (found out which one by supplying -t flag to ld). For some reason vers.c was not in the system-specific compile directory and not even mentioned in the Makefile. After fixing this the kernel linked without complaint. How robust is the filesystem with respect to crashes? -- Adam David (adamd@rhi.hi.is)