Date: Mon, 19 Sep 2005 18:44:08 -0400 From: Charles Swiger <cswiger@mac.com> To: pergesu@gmail.com Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Segmentation fault when building kdelibs Message-ID: <EA54115E-0B9E-4442-80F7-95E58EEE4285@mac.com> In-Reply-To: <810a540e05091915165d4a2041@mail.gmail.com> References: <810a540e05091818065f10356e@mail.gmail.com> <444q8gdd8g.fsf@be-well.ilk.org> <810a540e050919150428c0cea1@mail.gmail.com> <DB170ACE-B96A-4FE3-B469-EA71E10B07E2@mac.com> <810a540e05091915165d4a2041@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sep 19, 2005, at 6:16 PM, Pat Maddox wrote: > Happens in different spots, so I guess it's a hardware problem. But > what exactly am I looking for? Is it bad ram, a bad disk? How do I > find out what's messed up? CPU cooling or bad memory are likely culprits. Run memtest.org's checker overnight and see what that finds. memtest is also available as a port, I think, but I burned the .iso image they have and use that as a standalone bootable checker. If you have name-brand hardware, people like Dell and whatnot offer a diagnostics floppy or CD which can do useful testing, too... -- -Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EA54115E-0B9E-4442-80F7-95E58EEE4285>