Date: Fri, 19 Jun 2009 13:17:07 -0400 From: Glen Barber <glen.j.barber@gmail.com> To: Bruce Cran <bruce@cran.org.uk> Cc: freebsd-questions@freebsd.org Subject: Re: Processes dying with signal 11 Message-ID: <4ad871310906191017lddaaba3nfce8bb820af44e0c@mail.gmail.com> In-Reply-To: <20090619175537.36128909@gluon.draftnet> References: <20090619175537.36128909@gluon.draftnet>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jun 19, 2009 at 12:55 PM, Bruce Cran<bruce@cran.org.uk> wrote: > I've been trying to run a buildworld using the clangbsd branch on my > G4 iBook, but without success. I'm currently running a fairly > up-to-date HEAD: > > FreeBSD mac.draftnet 8.0-CURRENT #0: Tue Jun 16 22:07:11 BST 2009 > brucec@mac.draftnet:/usr/obj/usr/src/sys/IBOOK powerpc > > The problem I see is that after a few hours of running buildworld, when > it starts building clang itself, 'as' crashes with a signal 11. > > I'm wondering if this is the normal case of bad memory/HDD/CPU or > something else because it also causes several other processes to crash, > notably dhclient and sendmail, but I've also seen tcsh crash too. =A0I > created a test program which allocated 500MB memory to force the system > into swap (my iBook only has 512MB). =A0After a few minutes dhclient > crashed but the test program kept running. =A0Is this what normally > happens when hardware's going bad? > Unfortunately, yes. Does the build fail in the same place everytime? Usually hardware failure will cause randomly placed SIGSEGV errors. --=20 Glen Barber
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4ad871310906191017lddaaba3nfce8bb820af44e0c>