i still haven't been able to do a buildworld without cc segfaulting. :(

if i repeat the cc operation that segfaulted during buildworld with cc under /usr/bin everything works fine. the segfault only occurs during buildworld with the bootstrapped version of cc under /usr/ob/usr/src/tmp/usr/bin/cc.

i've replaced my /bin /sbin /lib /libexec /usr/bin /usr/sbin /usr/lib /usr/lib32 /usr/libdata /usr/libexec directories completely and recursively with ones built 19th of March (so the strlen bug should be fixed in all those files because they have been dynamically or statically linked gainst a good libc)

i've compared the output of `ident /usr/bin/cc` and `ident /usr/obj/usr/src/tmp/usr/bin/cc` and this is the result:

-/usr/bin/cc: +/usr/obj/usr/src/tmp/usr/bin/cc: $FreeBSD: src/lib/csu/amd64/crti.S,v 1.7 2004/03/21 01:39:01 peter Exp $ $FreeBSD: src/lib/csu/amd64/crtn.S,v 1.6 2004/03/21 01:39:01 peter Exp $ $FreeBSD: src/lib/csu/common/crtbrand.c,v 1.6 2007/12/04 12:18:43 kib Exp $ $FreeBSD: src/lib/csu/amd64/crt1.c,v 1.16 2010/03/05 13:28:05 uqs Exp $ $FreeBSD: src/lib/libc/string/strsignal.c,v 1.9 2010/01/24 10:35:26 ume Exp $ + $FreeBSD: src/lib/libc/amd64/string/memcmp.S,v 1.2 2008/11/02 01:10:54 peter Exp $ $FreeBSD: src/lib/libc/stdio/remove.c,v 1.9 2007/01/09 00:28:07 imp Exp $ $FreeBSD: src/lib/libc/stdio/freopen.c,v 1.21 2008/04/17 22:17:54 jhb Exp $ $FreeBSD: src/lib/libc/gen/waitpid.c,v 1.7 2007/01/09 00:27:56 imp Exp $ @@ -51,7 +52,6 @@ $FreeBSD: src/lib/libc/stdio/fread.c,v 1.17 2010/01/10 14:30:30 cperciva Exp $ $FreeBSD: src/lib/libc/stdio/fileno.c,v 1.13 2008/05/05 16:03:52 jhb Exp $ $FreeBSD: src/lib/libc/stdio/ferror.c,v 1.12 2008/05/05 16:03:52 jhb Exp $ - $FreeBSD: src/lib/libc/stdio/puts.c,v 1.11 2007/01/09 00:28:07 imp Exp $ $FreeBSD: src/lib/libc/gen/syslog.c,v 1.39 2007/01/09 00:27:55 imp Exp $ $FreeBSD: src/lib/libc/string/strstr.c,v 1.6 2009/02/03 17:58:20 danger Exp $ $FreeBSD: src/lib/libc/string/strlcpy.c,v 1.11 2009/02/28 05:15:02 das Exp $

i'm really clueless right now. i thought maybe this could be due to bad memory, but in that case shouldn't segfaults appear randomly? because this one is 100% reproducable. maybe a bad sector in my hdd? i don't know. :(

cheers. alex