Message395205
| Author |
kj |
| Recipients |
BTaskaya, WildCard65, ZackerySpytz, corona10, hroncok, kj, nascheme, ronaldoussoren, serhiy.storchaka, shihai1991, steve.dower, vstinner |
| Date |
2021年06月06日.11:12:42 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1622977963.0.0.573732403633.issue39573@roundup.psfhosted.org> |
| In-reply-to |
| Content |
@victor, git bisect tells me the change f3fa63ec75fdbb4a08a10957a5c631bf0c4a5970 caused test_exceptions.ExceptionTests.test_recursion_in_except_handler to stack overflow only on windows debug builds. 3 windows buildbots using python debug mode is affected. Python compiled with release mode is *not* affected and passes the test. Here's an example error on one of the buildbots:
https://buildbot.python.org/all/#/builders/596/builds/354/steps/4/logs/stdio
I can also reproduce this locally. I tracked this issue down after a recursion in AST also caused a stack overflow, see my message here:
https://bugs.python.org/msg395172
TLDR: Windows builds seems to set stack size to 2MB, on *nix it's probably higher (usually 8MB). I suspect the static inline functions are not being inlined in windows debug builds, so every function call adds to the stack. In that message I proposed to increase the stack size on windows but there are some concerns (see msg395177). What do you think? |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2021年06月06日 11:12:43 | kj | set | recipients:
+ kj, nascheme, ronaldoussoren, vstinner, serhiy.storchaka, steve.dower, hroncok, corona10, ZackerySpytz, WildCard65, BTaskaya, shihai1991 |
| 2021年06月06日 11:12:43 | kj | set | messageid: <1622977963.0.0.573732403633.issue39573@roundup.psfhosted.org> |
| 2021年06月06日 11:12:42 | kj | link | issue39573 messages |
| 2021年06月06日 11:12:42 | kj | create |
|