Hi, I narrowed down the problem a bit.
test_signal works fine when run standalone: $ ./build-static/python -Wd -3 -E -tt Lib/test/regrtest.py -w -l test_signal test_signal 1 test OK. However, if it's run after test___all___, it hangs: $ ./build-static/python -Wd -3 -E -tt Lib/test/regrtest.py -w -l test___all__ test_signal [... hang ] test___all__ does lots of things. Its purpose is to run the test routine in each of the modules in Lib/. I found that only one of these routines is responsible for the crash: idlelib. If you blacklist idlelib (see attachment), then test_signal doesn't crash. As this is most likely a bug in glibc, we need to keep shrinking the problem down. However, to get python out of FTBFS state, perhaps it'll be enough to either blacklist idlelib or disable test_signal. -- Robert Millan
idlelib.diff
Description: Binary data
