Subject: Re: Hardware or toolchain error?
To: None <email@example.com>
From: Murray Armfield <firstname.lastname@example.org>
Date: 10/15/2002 15:01:22
I have recently seen similar messages which were associated with funny
memory combinations. Sometimes a compile error, sometimes a panic,
usually in uvm, sometimes just hung. Was very random behaviour.
Can't say for sure, can you test with other ram?
> I'd really rather not think that the 512 MB DIMM I bought less than
> three months ago is bad, but it sure looks that way, unless
> someone's aware of toolchain problems that would produce the
> /ten/tools/bin/i386--netbsdelf-gcc -O2 -Wall -Wstrict-prototypes
> -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wreturn-type
> -Wswitch -Wshadow -Werror -I/ten/src/lib/libcurses
> -I/ten/src/lib/libterm -DCM_N -DCM_GT -DCM_B -DCM_D -nostdinc -isystem
> /ten/build/i386/usr/include -c -pg /ten/src/lib/libcurses/refresh.c -o
> refresh.po cc1 in free(): warning: modified (chunk-) pointer.
> [122 more times]
> i386--netbsdelf-gcc: Internal compiler error: program cc1 got fatal
> signal 11 *** Error code 1
> nbmake: stopped in /ten/src/lib/libcurses
> This is from a build.sh -B .. -D .. -O .. -R .. -T .. -m i386.
> (I've got a full log, but I won't waste bandwidth with it unless
> someone actually thinks this is something other than a hardware
> problem on my end.)
> gabriel rosenkoetter