you're right there tim, it is changing the place in the compile that it bombs at each time, doing the same buildworld, with the same source ! here some examples from NOW:

PS: i did a memtest "memtest 520m" (let it run for ~30min) with NO errors AND i did a cpuburn "burnP6" test for about ~15min with NO errors.... ?????

Server Hardware:

Compaq Proliant ML310
2x DDR 256MB, PC-2100 ECC Registered,266MHz, CL2.5
Intel Pentium IV 2.4 GHz
Compaq SMART-Array 221 SCSI RAID Controller with 3 hd's (3x 18GB ==> RAID5)


1st try: -----

cc -O -pipe -D_IEEE_LIBM -D_ARCH_INDIRECT=i387_ -c /usr/src/lib/msun/src/s_nextafter.c -o s_nextafter.o
cc -O -pipe -D_IEEE_LIBM -D_ARCH_INDIRECT=i387_ -c /usr/src/lib/msun/src/s_nextafterf.c -o s_nextafterf.o
cc -O -pipe -D_IEEE_LIBM -D_ARCH_INDIRECT=i387_ -c /usr/src/lib/msun/src/s_rint.c -o s_rint.o
cc -O -pipe -D_IEEE_LIBM -D_ARCH_INDIRECT=i387_ -c /usr/src/lib/msun/src/s_rintf.c -o s_rintf.o
cc: Internal compiler error: program cc1 got fatal signal 11
*** Error code 1


Stop in /usr/src/lib/msun.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
-bash-2.05b#

-----


2nd try: -----

usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/engine -I/usr/obj/usr/src/secure/lib/libcrypto -DOPENSSL_NO_IDEA -DL_ENDIAN -DNO_IDEA -c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/conf/conf_mod.c -o conf_mod.So
cc: cpp0: Internal compiler error: program cc1 got fatal signal 4output pipe has been closed


*** Error code 1

Stop in /usr/src/secure/lib/libcrypto.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
-bash-2.05b#

-----


3rd try: -----

cc -O -pipe -DTERMIOS -DANSI_SOURCE -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/engine -I/usr/obj/usr/src/secure/lib/libcrypto -DOPENSSL_NO_IDEA -DL_ENDIAN -DNO_IDEA -c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_bool.c -o a_bool.o
cc: Internal compiler error: program cc1 got fatal signal 11
*** Error code 1


Stop in /usr/src/secure/lib/libcrypto.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
-bash-2.05b#

-----

-bash-2.05b# tail -3 /var/log/messages
Mar 8 21:25:13 ns1 /kernel: pid 28902 (cc1), uid 0: exited on signal 11 (core dumped)
Mar 8 21:40:35 ns1 /kernel: pid 63920 (cc1), uid 0: exited on signal 4 (core dumped)
Mar 8 21:48:11 ns1 /kernel: pid 92714 (cc1), uid 0: exited on signal 11 (core dumped)
-bash-2.05b#




taxman wrote:
On Friday 07 March 2003 04:00 pm, Thomas Haug wrote:

Hi List members

Since a few weeks my box is core dumping when i'm doing a make
buildworld with
one of the following error msgs (changing always :-)):


If it is changing the place in the compile that it bombs at each time, doing the same buildworld, with the same source, then you have a *high* likelihood of hardware error of some sort. Try doing the exact same buildworld two or three times in a row, does it bomb every time? Same spot or different?
You didn't show enough of the error to let us know that
try using script to record the output of the build then you can include more of the error in your mail if needed.



Mar  5 21:54:17 ns1 /kernel: pid 34726 (cc1), uid 0: exited on signal 4
(core
dumped)
Mar  5 22:10:21 ns1 /kernel: pid 5383 (cc1), uid 0: exited on signal 11
(core
dumped)
Mar  5 22:10:21 ns1 /kernel: pid 5384 (as), uid 0: exited on signal 5 (core
dumped)

This box is running since a year, so its pritty new and i never had
problems
with it. Every appl is running fine, nothing is core dumping, just the make
buildworld does...


That could easily be because buildworld stresses your system more and in different ways than most other apps.

Tim




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Reply via email to