Armin Rigo <[email protected]> added the comment: traceback2.txt contains a complete traceback with, at the bottom, the function that should not release the GIL (here Logger.log_loop), with every function before being potentially called (so actually in the reverse order as a regular Python traceback), ending at the top at a function that actually releases the GIL (here ccall_fstat64_..). In this case the bogus part is near the end: get_printable_location() calls PyCode.get_repr, which on "default" does not call anything else, but which in the py3k branch calls space.fsdecode_w() which can indirectly call anything at all. You need to fix this get_printable_location(). (Note that it's only used for debugging anyway.)
________________________________________ PyPy bug tracker <[email protected]> <https://bugs.pypy.org/issue1603> ________________________________________ _______________________________________________ pypy-issue mailing list [email protected] https://mail.python.org/mailman/listinfo/pypy-issue
