Hi Armin and Matti, now my project works.
So concerning current stock installation of pypy seems that the only problem was a lack of sufficient stack space on windows, in debug pypy is configured to increase stack, but in release it is not. And as stack space is insufficient - some code might crash on windows (on linux stack is by default is bigger - so no problem occurs ). while I'm preparing my changes, is it possible, that current code is changed that pypy on windows is compiled in release build with increased stack, possibly even some more, than currently in debug mode? another point. while compiling pypy lack of memory is an issue even on machines with more memory that required for compilation. Basically pypy will crash when achieves 2 Gb memory limit even with setting pypy to use extended memory I suppose it starts to interfere with system memory addresses which are located exactly at 2 Gb starting point, but VirtualAlloc allows explicitly to allocate memory from higher addresses and avoid system memory clashes when memory is continuously allocated. Here - one change would be required ( which I would not attempt now as have insufficient knowledge of pypy internals ) to use not a stock malloc, but a redefined (wrapper) malloc which will call to windows VirtualAlloc with appropriate MEM_TOP_DOWN flag. The flag could be passed to pypy in command line to indicate, that memory should be allocated from top. Then on machines which have enough memory ( I have 8 Gb - but pypy will still report memory error when compiling itself ) there will not be memory problems. Best regards Sergey _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
