Bug#743141: system hangs when building gcc on kfreebsd-amd64
On 25/04/14 18:38, Petr Salinger wrote:
> I tested it:
> system up-to-date jessie, with kfreebsd-image-10.0-1-amd64/10.0-4
Same here. I used a plain ufs filesystem and no swap.
> It seems to be during test of "gcc unix/-m32".
Yes. I reproduced this with kernel messages going to a serial console
(booted with -D). Manually triggering a panic (sysctl
debug.kdb.panic=1) normally outputs a stack trace from KDB to serial,
but this crash did not. I think it rebooted instantly. Obviously
nothing is logged to syslog either.
I was building gcc-4.7 with -j1 as a non-root user from a remote SSH
session, so I had a record of the very last console messages:
> Running target unix/-m32
> Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
> Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
> Using /home/steven/gcc-4.7-4.7.3/src/gcc/testsuite/config/default.exp as tool-and-target-specific interface file.
> Running /home/steven/gcc-4.7-4.7.3/src/gcc/testsuite/gcc.c-torture/compile/compile.exp ...
This is the third part of the gcc testsuite. Previous sections are
called "unix" and "unix/-fstack-protector"; both of those had finished
before this.
It seems possible to get much more output during the testsuite by
creating a ~/.dejagnurc containing "set verbose 2". I've started
another run of this now but it may take several hours.
Regards,
--
Steven Chamberlain
steven@pyro.eu.org
Reply to: