[issue15761] Setting PYTHONEXECUTABLE can cause segfaults on OS X

Changes by Ronald Oussoren : -- resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker ___ ___

[issue15761] Setting PYTHONEXECUTABLE can cause segfaults on OS X

Ronald Oussoren added the comment: committed a patch in revisions 526c6262d91f and ae51329f9893. Those won't end up as messages in this issue due to a typo in the check-in message. -- ___ Python tracker __

[issue15761] Setting PYTHONEXECUTABLE can cause segfaults on OS X

Changes by Ronald Oussoren : -- versions: +Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue15761] Setting PYTHONEXECUTABLE can cause segfaults on OS X

Ronald Oussoren added the comment: I can now reproduce the isue: env PYTHONHOME=/Library/Frameworks/Python.framework/Versions/3.3 PYTHONEXECUTABLE=/bin/bash MallocGuardEdges=1 MallocStackLogging=1 MallocScribble=1 MallocStackLoggingNoCompact=1 MallocCheckHeapEach=1 arch -i386 python3.3 -c '

[issue15761] Setting PYTHONEXECUTABLE can cause segfaults on OS X

Ronald Oussoren added the comment: There could be an off by one error in the decoding of PYTHONEXECUTABLE, mbstowcs will only add a NUL character when there is room for one and when the environment variable is all ASCII the buffer isn't large enough which means the argument to Py_SetProgramNam

[issue15761] Setting PYTHONEXECUTABLE can cause segfaults on OS X

New submission from Ned Deily: Setting the environment variable PYTHONEXECUTABLE can cause the interpreter to crash with a segfault or to otherwise fail during initialization. Another manifestation is the failure of test test_osx_env with: AssertionError: -10 != 2 : expected PYTHONEXECUTABLE