diff options
author | Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> | 2019-07-02 00:48:59 -0700 |
---|---|---|
committer | Ned Deily <nad@python.org> | 2019-07-02 03:48:59 -0400 |
commit | 782854f90ad5f73f787f68693d535f2b05514e13 (patch) | |
tree | 7d88bba5332553bf78061444bc1b586ec3280703 /config.guess | |
parent | 29d6905826d4417426e70f6209ca5e0db7921685 (diff) | |
download | cpython-git-782854f90ad5f73f787f68693d535f2b05514e13.tar.gz |
bpo-34602: Avoid failures setting macOS stack resource limit (GH-14546) (GH-14549)
Under some conditions the earlier fix for bpo-18075, "Infinite recursion
tests triggering a segfault on Mac OS X", now causes failures on macOS
when attempting to change stack limit with resource.setrlimit
resource.RLIMIT_STACK, like regrtest does when running the test suite.
The reverted change had specified a non-default stack size when linking
the python executable on macOS. As of macOS 10.14.4, the previous
code causes a hard failure when running tests, although similar
failures had been seen under some conditions under some earlier
systems. Reverting the change to the interpreter stack size at link
time helped for release builds but caused some tests to fail when
built --with-pydebug. Try the opposite approach: continue to build
the interpreter with an increased stack size on macOS and remove
the failing setrlimit call in regrtest initialization. This will
definitely avoid the resource.RLIMIT_STACK error and should have
no, or fewer, side effects.
(cherry picked from commit 5bbbc733e6cc0804f19b071944af8d4719e26ae6)
Co-authored-by: Ned Deily <nad@python.org>
Diffstat (limited to 'config.guess')
0 files changed, 0 insertions, 0 deletions