Re: buildworld seg faulting.
On Monday, 01 September 2003 23:02, Bill Moran wrote: Alastair G. Hogge wrote: On Monday, 01 September 2003 02:24, Steve Kargl wrote: On Sun, Aug 31, 2003 at 07:52:15PM +1000, Alastair G. Hogge wrote: Hello list, For the past couple of weeks I've been tyring to keep my system up to date with cvsup. However, when ever I run a buildworld I get problems with gcc (I think it's gcc). I've tried nuking /usr/obj and running make clean many tims before each build but this doesn't help. What I've noticed is that the seg fault doesn't occur in the same place. There isn't enough context in the error messages you reported. Are you using the -j option during your buildworld? No. just plain old make buildworld i did also try -j3 However, your last sentence in the above quoted paragraph, suggests that you have bad memory or a heating problem or a suspect power supply. Ahhh. I don't like the sound of that. Is there something else I'm leaving out. I really hope it isn't memory I sold my thumbs to get 512megs of Corsair XSM :-( Download memtest86 and let it run for a couple of hours. If you see any errors at all, try and get that memory replaced under warranty. OK install memtest from the ports. After running /usr/bin/nice -35 memtest 512m 2 --log I got: Current limits: RLIMIT_RSS 0x RLIMIT_VMEM 0x Raising limits... Unable to malloc 536870912 bytes. Allocated 535822336 bytes...trying mlock...failed: insufficient resources. Allocated 534773760 bytes...trying mlock...failed: insufficient resources. Allocated 533725184 bytes...trying mlock...failed: insufficient resources. Allocated 532676608 bytes...trying mlock...failed: insufficient resources. Allocated 531628032 bytes...trying mlock...failed: insufficient resources. Allocated 530579456 bytes...trying mlock...failed: insufficient resources. Allocated 529530880 bytes...trying mlock...failed: insufficient resources. Allocated 528482304 bytes...trying mlock...failed: insufficient resources. Allocated 527433728 bytes...trying mlock...failed: insufficient resources. Allocated 526385152 bytes...trying mlock...failed: insufficient resources. Allocated 525336576 bytes...trying mlock...failed: insufficient resources. Allocated 524288000 bytes...trying mlock...failed: insufficient resources. Allocated 523239424 bytes...trying mlock...failed: insufficient resources. Allocated 522190848 bytes...trying mlock...failed: insufficient resources. Allocated 521142272 bytes...trying mlock...failed: insufficient resources. Allocated 520093696 bytes...trying mlock...failed: insufficient resources. Allocated 519045120 bytes...trying mlock...failed: insufficient resources. Allocated 517996544 bytes...trying mlock...failed: insufficient resources. Allocated 516947968 bytes...trying mlock...failed: insufficient resources. Allocated 515899392 bytes...trying mlock...failed: insufficient resources. Allocated 514850816 bytes...trying mlock...failed: insufficient resources. Allocated 513802240 bytes...trying mlock...failed: insufficient resources. Allocated 512753664 bytes...trying mlock...failed: insufficient resources. Allocated 511705088 bytes...trying mlock...failed: insufficient resources. Allocated 510656512 bytes...trying mlock...failed: insufficient resources. Allocated 509607936 bytes...trying mlock...failed: insufficient resources. Allocated 508559360 bytes...trying mlock...failed: insufficient resources. Allocated 507510784 bytes...trying mlock...failed: insufficient resources. Allocated 506462208 bytes...trying mlock...failed: insufficient resources. Allocated 505413632 bytes...trying mlock...failed: insufficient resources. Allocated 504365056 bytes...trying mlock...failed: insufficient resources. Allocated 503316480 bytes...trying mlock...failed: insufficient resources. Allocated 502267904 bytes...trying mlock...failed: insufficient resources. Allocated 501219328 bytes...trying mlock...failed: insufficient resources. Allocated 500170752 bytes...trying mlock...failed: insufficient resources. Allocated 499122176 bytes...trying mlock...failed: insufficient resources. Allocated 498073600 bytes...trying mlock...failed: insufficient resources. Allocated 497025024 bytes...trying mlock...failed: insufficient resources. Allocated 495976448 bytes...trying mlock...failed: insufficient resources. Allocated 494927872 bytes...trying mlock...failed: insufficient resources. Allocated 493879296 bytes...trying mlock...failed: insufficient resources. Allocated 492830720 bytes...trying mlock...failed: insufficient resources. Allocated 491782144 bytes...trying mlock...failed: insufficient resources. Allocated 490733568 bytes...trying mlock...failed: insufficient resources. Allocated 489684992 bytes...trying mlock...failed: insufficient resources. Allocated 488636416 bytes...trying mlock...failed: insufficient resources. Allocated 487587840 bytes...trying mlock...failed: insufficient resources. Allocated
Re: buildworld seg faulting.
On Monday, 01 September 2003 02:24, Steve Kargl wrote: On Sun, Aug 31, 2003 at 07:52:15PM +1000, Alastair G. Hogge wrote: Hello list, For the past couple of weeks I've been tyring to keep my system up to date with cvsup. However, when ever I run a buildworld I get problems with gcc (I think it's gcc). I've tried nuking /usr/obj and running make clean many tims before each build but this doesn't help. What I've noticed is that the seg fault doesn't occur in the same place. There isn't enough context in the error messages you reported. Are you using the -j option during your buildworld? No. just plain old make buildworld i did also try -j3 However, your last sentence in the above quoted paragraph, suggests that you have bad memory or a heating problem or a suspect power supply. Ahhh. I don't like the sound of that. Is there something else I'm leaving out. I really hope it isn't memory I sold my thumbs to get 512megs of Corsair XSM :-( -Al ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld seg faulting.
Alastair G. Hogge wrote: On Monday, 01 September 2003 02:24, Steve Kargl wrote: On Sun, Aug 31, 2003 at 07:52:15PM +1000, Alastair G. Hogge wrote: Hello list, For the past couple of weeks I've been tyring to keep my system up to date with cvsup. However, when ever I run a buildworld I get problems with gcc (I think it's gcc). I've tried nuking /usr/obj and running make clean many tims before each build but this doesn't help. What I've noticed is that the seg fault doesn't occur in the same place. There isn't enough context in the error messages you reported. Are you using the -j option during your buildworld? No. just plain old make buildworld i did also try -j3 However, your last sentence in the above quoted paragraph, suggests that you have bad memory or a heating problem or a suspect power supply. Ahhh. I don't like the sound of that. Is there something else I'm leaving out. I really hope it isn't memory I sold my thumbs to get 512megs of Corsair XSM :-( Download memtest86 and let it run for a couple of hours. If you see any errors at all, try and get that memory replaced under warranty. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld seg faulting.
On Sun, Aug 31, 2003 at 07:52:15PM +1000, Alastair G. Hogge wrote: Hello list, For the past couple of weeks I've been tyring to keep my system up to date with cvsup. However, when ever I run a buildworld I get problems with gcc (I think it's gcc). I've tried nuking /usr/obj and running make clean many tims before each build but this doesn't help. What I've noticed is that the seg fault doesn't occur in the same place. There isn't enough context in the error messages you reported. Are you using the -j option during your buildworld? However, your last sentence in the above quoted paragraph, suggests that you have bad memory or a heating problem or a suspect power supply. -- Steve ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
buildworld seg faulting.
Hello list, For the past couple of weeks I've been tyring to keep my system up to date with cvsup. However, when ever I run a buildworld I get problems with gcc (I think it's gcc). I've tried nuking /usr/obj and running make clean many tims before each build but this doesn't help. What I've noticed is that the seg fault doesn't occur in the same place. The following is snippets of two errors. === gnu/usr.bin/binutils/size /usr/obj/usr/src/gnu/usr.bin/binutils/size created for /usr/src/gnu/usr.bin/binu tils/size Segmentation fault (core dumped) *** Error code 139 Stop in /usr/src/gnu/usr.bin/binutils. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 Stop in /usr/src/gnu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 And: insn-opinit.c: In function `init_all_optabs': insn-opinit.c:510: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See URL:http://gcc.gnu.org/bugs.html for instructions. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/cc_int. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. My current uname -a reports: FreeBSD nova 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sat Aug 16 12:32:29 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NOVA i386 I was able to buildworld once a week ago. After each seg fault I would just continue the build again with out cleaning out the object files. Thanks in advance -Al ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
