Just to explicitly ask for it: Svante Signell, le Tue 06 May 2014 10:06:49 +0200, a écrit : > For some (yet) unknown reason all libgo tests fails with a segfault when > run in the build tree: make, sh or something else, the test commands are > rather hard to track.
Doesn't that dump a core? Do you have /servers/crash properly pointing to /servers/crash-dump-core and ulimit -u set to unlimited? > However, running the tests manually, sigh!, after installing gccgo and > libgo5 from gcc-4.9-4.9.0-1 with split stack support the result is as > follows: > > Total: 122 > PASS: 95 > FAIL: 27 Good! :) > Number of tests succeeding with libpthread's stack guard fixed: 33 (and > the other libc fixes) I'm not sure to understand: does it mean only 33 pass instead of 95? > Note: In many of the failing tests, only a small subset of each test > fails. Ok, that's a good sign. Samuel