Re: gcc segmentation fault in going back to current

From: Ben Kaduk (minimarmot_at_gmail.com)
Date: 09/20/05

  • Next message: Daniel O'Connor: "Re: Threading/KSE problem" 
    Date: Tue, 20 Sep 2005 02:29:41 +0000
To: Chuck Robey <chuckr@chuckr.org>

    On 9/19/05, Chuck Robey <chuckr@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@freebsd.org mailing list
    > http://lists.freebsd.org/mailman/listinfo/freebsd-current
    > To unsubscribe, send any mail to "freebsd-current-unsubscribe@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.

    Ben Kaduk
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

  • Next message: Daniel O'Connor: "Re: Threading/KSE problem"