[issue8719] buildbot: segfault on FreeBSD (signal 11)

STINNER Victor added the comment: > That may be what you meant, but "installed on this host" made me think > I could do something external on the buildbot which I don't > think would work given that the module has to be called from within > the tests themselves? If you install faulthandler on

[issue8719] buildbot: segfault on FreeBSD (signal 11)

Changes by Mark Dickinson : -- nosy: +mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue8719] buildbot: segfault on FreeBSD (signal 11)

David Bolen added the comment: Wouldn't that module have to be put into the actual source tree, since the tests run beneath the interpreter/libraries that are built for the test? That may be what you meant, but "installed on this host" made me think I could do something external on the buildb

[issue8719] buildbot: segfault on FreeBSD (signal 11)

STINNER Victor added the comment: https://github.com/haypo/faulthandler/wiki can be tried on this buildbot to get more information about this issue. But the module have to be installed on this host. -- ___ Python tracker

[issue8719] buildbot: segfault on FreeBSD (signal 11)

Stefan Krah added the comment: I ran a test --without-threads: test_runpy and test_exceptions passed, test_sys was not reached: test_sqlite Fatal error 'Cannot allocate red zone for initial thread' at line 384 in file /usr/src/lib/libthr/thread/thr_init.c (errno = 12) *** Signal 6 No Signal

[issue8719] buildbot: segfault on FreeBSD (signal 11)

New submission from STINNER Victor : There are segfaults on x86 FreeBSD 7.2 3.x. It looks like it's a regression introduced by r80876. --- Build 556: ... test_coding test_hash test_strtod test_float test_runpy *** Signal 11 Build 555: ... test_int test_smtplib test_asynchat test_runpy *** Sig