Bug#743141: system hangs when building gcc on kfreebsd-amd64
On 11/05/14 18:18, Petr Salinger wrote:
> I tried under plain FreeBSD kernel (via kfreebsd-downloader-10)
> and it does not reboot for me.
It still crashes reproducibly for me, on upstream's build of:
GNU/kFreeBSD debian 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu
Jan 16 22:34:59 UTC 2014
root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC x86_64
I deleted all tests except for
src/gcc/testsuite/gcc.c-torture/compile/pr44686.c
and then:
> steven@debian:~/gcc-4.7-4.7.3/build/gcc$ make check RUNTESTFLAGS='--target_board "unix/-m32" -v -v'
...
> Testing gcc.c-torture/execute/builtins/20010124-1.c, -O0
> doing compile
> Invoking the compiler as /home/steven/gcc-4.7-4.7.3/build/gcc/xgcc -B/home/steven/gcc-4.7-4.7.3/build/gcc/ /home/steven/gcc-4.7-4.7.3/src/gcc/testsuite/gcc.c-torture/execute/builtins/20010124-1.c /home/steven/gcc-4.7-4.7.3/src/gcc/testsuite/gcc.c-torture/execute/builtins/20010124-1-lib.c /home/steven/gcc-4.7-4.7.3/src/gcc/testsuite/gcc.c-torture/execute/builtins/lib/main.c -w -O0 -lm -m32 -o /home/steven/gcc-4.7-4.7.3/build/gcc/testsuite/gcc/20010124-1.x0
> Setting timeout to 300
> Executing on host: /home/steven/gcc-4.7-4.7.3/build/gcc/xgcc -B/home/steven/gcc-4.7-4.7.3/build/gcc/ /home/steven/gcc-4.7-4.7.3/src/gcc/testsuite/gcc.c-torture/execute/builtins/20010124-1.c /home/steven/gcc-4.7-4.7.3/src/gcc/testsuite/gcc.c-torture/execute/builtins/20010124-1-lib.c /home/steven/gcc-4.7-4.7.3/src/gcc/testsuite/gcc.c-torture/execute/builtins/lib/main.c -w -O0 -lm -m32 -o /home/steven/gcc-4.7-4.7.3/build/gcc/testsuite/gcc/20010124-1.x0 (timeout = 300)
> pid is 2166 -2166
> waitres is 2166 exp8 0 0
> output is status 0
> Checking pattern "sparc-*-sunos*" with x86_64-pc-kfreebsd-gnu
> Checking pattern "alpha*-*-*" with x86_64-pc-kfreebsd-gnu
> Checking pattern "hppa*-*-hpux*" with x86_64-pc-kfreebsd-gnu
> Checking pattern "sparc-*-sunos*" with x86_64-pc-kfreebsd-gnu
> Checking pattern "alpha*-*-*" with x86_64-pc-kfreebsd-gnu
> Checking pattern "hppa*-*-hpux*" with x86_64-pc-kfreebsd-gnu
> Checking "spu-*-*" against "x86_64-pc-kfreebsd-gnu"
> Checking x86_64-pc-kfreebsd-gnu against x86_64-pc-kfreebsd-gnu
> loading to unix/-m32
> Setting LD_LIBRARY_PATH to :/home/steven/gcc-4.7-4.7.3/build/gcc:/home/steven/gcc-4.7-4.7.3/build/gcc/32::/home/steven/gcc-4.7-4.7.3/build/gcc:/home/steven/gcc-4.7-4.7.3/build/gcc/32
> spawning command /home/steven/gcc-4.7-4.7.3/build/gcc/testsuite/gcc/20010124-1.x0
<reboots immediately>
This even works inside of a BSD jail.
After a reboot, 20010124-1.x0 was missing. Even though the filesystem
is UFS, mounted with the sync option.
I can compile it by hand, then run it with the LD_LIBRARY_PATH as above,
but it doesn't trigger the crash that way.
I'd really like to go to upstream with this, but the testcase is
currently "a full Debian GNU/kFreeBSD sid chroot, a fully built GCC-4.7
source tree and all build dependencies" and I think we need to find
something smaller.
Regards,
--
Steven Chamberlain
steven@pyro.eu.org
Reply to: