Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!news.ececs.uc.edu!newsfeeds.sol.net!news.maxwell.syr.edu!news.mathworks.com!fu-berlin.de!gusw.dialup.fu-berlin.DE!not-for-mail From: Gunther Schadow <gunther@gusw.dialup.fu-berlin.de> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Can hardware problems result in SIGSEGV and SIGBUS? Date: Sun, 16 Feb 1997 18:13:07 +0100 Organization: Freie Universitaet Berlin Lines: 22 Message-ID: <33074023.41C67EA6@gusw.dialup.fu-berlin.de> NNTP-Posting-Host: gusw.dialup.fu-berlin.de (160.45.216.109) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Access: 16 17 19 267 X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.1.0-RELEASE i386) Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:35539 Hi friends, can you imagin a broken hardware as the cause of busy processes getting killed rather randomly with SIGSEGV and SIGBUS? For some days now, I get these errors from GCC when I compile rather big sources, like GCC itself. But it is not just GCC, each program that is busy enough using some more memory. I double checked that there *is* enough swap space, swapinfo reporting only 16% useage. I recompiled my kernel (2.1.0-RELEASE) and installed it again. Even programs that only use libc.so are crashing. I am completely stucked! Do I have to replace hardware components? A new processor? How can I test this, I mean, I do not have the mony to buy a new i586/133 just to see that the new one does not help. any hints are appreciated, -Gunther -- Gunther Schadow-----------Windsteiner Weg 54a, Berlin 14165, FR. Germany Dept. of Anaesthesia, Benjamin Franklin Univerity Hospital, Berlin. gusw@fub46.zedat.fu-berlin.de http://userpage.fu-berlin.de/~gusw ----------------------------------#include <usual/disclaimer>-----------