Date: Mon, 19 Sep 2005 16:16:26 -0600 From: Pat Maddox <pergesu@gmail.com> To: Charles Swiger <cswiger@mac.com>, FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Segmentation fault when building kdelibs Message-ID: <810a540e05091915165d4a2041@mail.gmail.com> In-Reply-To: <DB170ACE-B96A-4FE3-B469-EA71E10B07E2@mac.com> References: <810a540e05091818065f10356e@mail.gmail.com> <444q8gdd8g.fsf@be-well.ilk.org> <810a540e050919150428c0cea1@mail.gmail.com> <DB170ACE-B96A-4FE3-B469-EA71E10B07E2@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/19/05, Charles Swiger <cswiger@mac.com> wrote: > On Sep 19, 2005, at 6:04 PM, Pat Maddox wrote: > >> The obvious question is: does it always fail at the same point? If > >> not, then it's almost certainly a hardware problem. If it does, then > >> a bit more information on your system would be needed, including how > >> you updated the ports skeletons, and whether you tried updating them > >> again since you first saw the problem. And if you aren't already, > >> try > >> using the system compiler to build the port. > > > > I've had a couple people suggest that it may be a hardware problem - > > what should I be looking for? >=20 > Pretty much what was quoted above. :-) >=20 > If you run the same build twice, does the compiler crash at the same > place, or in a different place? If the crash happens somewhere else > each time, it's probably hardware. >=20 > -- > -Chuck >=20 >=20 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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?810a540e05091915165d4a2041>