Hi, On 10/05/14 15:52, Christoph Egger wrote: > Steven Chamberlain <steven@pyro.eu.org> writes: >> Everything can be deleted from >> ~/gcc-4.7-4.7.3/src/gcc/testsuite/gcc.c-torture/compile/ except for >> pr44686.c, which necessitates building tls_runtime, which triggers the >> bug immediately. > Did you manage to figure something additional out? Do we know if this > also kills plain freebsd? I'm afraid I'm stuck with this. I narrowed it down to that particular test (or prerequisites of the test) when executed by the GCC testsuite. A large chroot is needed, having all the GCC build-deps; once GCC is finished building it's fairly easy to trigger this on demand. Even if it might trigger the bug on plain FreeBSD, I think all this is too unwieldy to provide as a testcase yet (0.5GiB for the GNU/kFreeBSD chroot and 4GiB for the GCC build tree). I'm still not sure exactly how the test is invoked by the testsuite's expect scripts; which executable, with what arguments, libraries, and how everything was compiled. My next idea is to try wheezy on kfreebsd-9 (perhaps built with LOCK_DEBUG etc.?), because Ivo showed a screenshot with some kernel output and a hang. Whereas kfreebsd-10 seems to reboot instantly and not output anything; even the older builds for experimental which had some extra debug options enabled. Regards, -- Steven Chamberlain steven@pyro.eu.org
Attachment:
signature.asc
Description: OpenPGP digital signature