gcc segmentation fault in going back to current
minimarmot at gmail.com
Mon Sep 19 19:29:43 PDT 2005
On 9/19/05, Chuck Robey <chuckr at chuckr.org> wrote:
> I just finally got back on the net after a move (my dsl unraveled itself
> for a while) ... I tried to bring my rather too old current really back
> to current (it was a couple months out of date, and I got a suprise ...
> I was greeted with a seegmentation fault from gcc whilst rebuilding gcc
> itself. I went thru the UPDATING, and did a 30 minutess spin thru the
> mailing lists I'd missed, but didn't find anything I'd missed ... if
> there is any obvious problem that's come and gone in the last 60 days,
> I'd really appreciate a whack to the head over it.
> Oh, in case it's important, it's in a Pentium-4 based box, several scsi
> disks, one ide one. The box usually runs my mail along with hobby work.
> freebsd-current at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
How do you feel about running memtest86? The general consensus in the past
has been that such errors are usually indicative of bad hardware.
More information about the freebsd-current