[issue25276] Intermittent segfaults on PPC64 AIX 3.x

STINNER Victor added the comment: The origin of the crash is unknown. Since I didn't see the crash recently, I close the issue. -- resolution: -> out of date status: open -> closed ___ Python tracker

[issue25276] Intermittent segfaults on PPC64 AIX 3.x

Stefan Krah added the comment: > It's possible that Python needs to be built with special options to allow > additional malloc space (-bmaxdata:0xN000). It seems to be the case, see Misc/README.AIX. This could explain the MemoryErrors, but not the segfaults. Are computed-gotos stable on

[issue25276] Intermittent segfaults on PPC64 AIX 3.x

David Edelsohn added the comment: Misc/README.AIX comments about XLC do not apply to GCC. One can adjust the memory space at normal link time with -Wl,-bmaxdata:0xN000. This trades off heap for shared memory segments. One does not need the extra ldedit stop, which stuffs the same value

[issue25276] Intermittent segfaults on PPC64 AIX 3.x

David Edelsohn added the comment: As we have seen with similar issues on other targets, this likely is due to the random order of tests. In another case, the timezone was not being restored properly by GLIBC. Another test is leaving the process in a state that somehow evokes this failure

[issue25276] Intermittent segfaults on PPC64 AIX 3.x

Stefan Krah added the comment: If you have time, you could use an explicit seed (and gdb): # test_email segfault: ./python -m test -j 1 -u all -W --randseed 5634141 -- ___ Python tracker

[issue25276] Intermittent segfaults on PPC64 AIX 3.x

Stefan Krah added the comment: And the segfaults are apparently somewhat random. This is beginning to look like an issue unrelated to decimal that was perhaps recently introduced (in which case "hg bisect" would be the fastest way to debug).

[issue25276] Intermittent segfaults on PPC64 AIX 3.x

STINNER Victor added the comment: I suggest to isolate tests using -j1: see my issue #25285. (Currently, -j1 doesn't use subprocesses.) -- ___ Python tracker