Re: SEGV (was Re: Internal compiler error on m68k for gcc-4.6)
On 2012-12-02 01:37, Thorsten Glaser wrote:
Well, as I said: I can run some memory testing tomorrow. This, of
course, doesn't guarantee that the memory is without any faults, if
nothing pops up. Only if something is found, then it's sure that the
memory is faulty. But what if the test won't show memory issues? I'll
Right, could be disc, bus, Elko, etc. or…
On three different machines the same symptom? Unlikely, I guess... ;-)
start another try on a second machine in the meanwhile. Schroot
segfaults there as well, but I can try the same on my third machine.
hardly doubt that the memory is causing the same issues in 3
machines. That's why I believe it's a toolchain problem...
… something like that, indeed. I’d guess it would have popped up by
now somehow though, especially as gcc is tested on bare metal, espe-
cially Coldfire, regularily…
The machines are 060s. What does Aranym emulate? 040? 030?
Another guess, is there enough RAM?
128M memory and >400M swap.
Also, what happens if you run the segfaulting command repeatedly?
You mean the compiler command? You mean I should rerun
gcc -c -g -fkeep-inline-functions -DIN_GCC -W -Wall -Wwrite-strings
-Wcast-qual -Wstrict-prototypes -Wmissing-prototypes
-Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros
-Wno-overlength-strings -Wold-style-definition -Wc++-compat
-DHAVE_CONFIG_H -I. -I. -I../../src/gcc -I../../src/gcc/.
-I../libdecnumber ../../src/gcc/stor-layout.c -o stor-layout.o
... from what directory? Base dir of build where I would have started
dpkg-buildpackage as well?
Ciao... // Fon: 0381-2744150
. Ingo \X/ http://blog.windfluechter.net
gpg pubkey: http://www.juergensmann.de/ij_public_key.