Steve Dower added the comment:
I get stack overflows all the way back to 3.7, so it's probably not anything
new. But our stack overflow detection is clearly not going to catch this case.
It's really only set up for a direct call within Python code, but this is going
through many more steps.
Steve Dower added the comment:
I guess we've got a new path through the interpreter loop that takes more stack
space than before and isn't part of our existing recursion tests.
It's probably somewhere in the vector call changes. Capturing the stack at
overflow point should show us - I'll see
New submission from Alejandro Reimondo :
The py8.py file starts a S8 system, a Smalltalk system running on Python
runtime, I am actually developing (in Beta).
The system is running w/o problems on OSX systems, but crash (fast exit w/o any
information) when running on Windows.
The crash occurs
