Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!bunyip.cc.uq.oz.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!news.kei.com!sol.ctr.columbia.edu!howland.reston.ans.net!gatech!pitt!w2xo!durham From: durham@w2xo.pgh.pa.us (Jim Durham) Newsgroups: comp.os.386bsd.questions Subject: gcc 1.39 on FreeBSD fixes core dumps. Keywords: gcc FreeBSD core-dumps Message-ID: <14@w2xo.pgh.pa.us> Date: 24 Dec 93 04:51:46 GMT Lines: 30 Here is a posting I made concerning gcc on FreeBSD. >Gcc crashes with signal 10 and signal 11. These are "BUS ERROR" >and "SEGMENTATION VIOLATION". There seems to be no logical pattern to >these occurences. Sometimes , while compiling a particular C >source file, gcc will die with signal 10, the, upon trying again on the >same source file, it will die with signal 11, then , on another try, it >will compile. Sounds like an unitialized pointer somewhere in gcc, for >a guess. Anyone else had this problem? Earlier, I posted several replies to this posting. I recently noticed a binary distribution for "gcc1" in the freebsd.cdrom.com archive. Since it was gcc1 that was crashing, I grabbed it and discovered that it was actually a binary distribution of the gcc 1.39 compiler. The compiler that comes with FreeBSD seems to be 2.4 . I replaced the failing compiler with the 1.39 version and *voila!*.. no more core dumps. Thanks to those who put this out there. I guess if you have 8 megs or more, the "stock" gcc compiler will do just fine, but , with my 4 megs, the 1.39 saved the day! I can actually work on code now..! Maybe this will be of help to someone with the same problems.. -Jim Durham