[issue22561] PyUnicode_InternInPlace crashes

Ned Deily added the comment: Also note that there were major internal changes in Python strings for 3.3 (http://legacy.python.org/dev/peps/pep-0393/) so you might want to look at those especially if this worked OK with Python 3.2. Since it seems unlikely that there would be any further progre

[issue22561] PyUnicode_InternInPlace crashes

STINNER Victor added the comment: > Shall I bounce this issue back to the LibreOffice folks and see if I can find > whoever owns that piece of code? (If anybody does...) For me, it's an issue in the uno module. -- ___ Python tracker

[issue22561] PyUnicode_InternInPlace crashes

Jens Troeger added the comment: Thanks Victor. I had the suspicion that UNO might set up somewhat incorrectly, and consequently cause this problem. To answer your questions: - Debug symbols: agreed. I haven't built a vanilla Python with symbols yet. I'm using MacPorts default Python 3.3. - Y

[issue22561] PyUnicode_InternInPlace crashes

STINNER Victor added the comment: It looks like a bug in the uno module, nobody reports this issue with the vanilla Python. The gdb traceback is incomplete: function parameters are missing, there are some unknown frames ("??"): #0 0x011c118d in PyUnicode_InternInPlace () from /Applicatio

[issue22561] PyUnicode_InternInPlace crashes

Changes by Serhiy Storchaka : -- assignee: -> ronaldoussoren components: +Macintosh nosy: +hynek, ned.deily, ronaldoussoren ___ Python tracker ___ __

[issue22561] PyUnicode_InternInPlace crashes

New submission from Jens Troeger: This might be an issue with Python, or an issue with Libre/OpenOffice not setting up the UNO environment correctly. The crash happens during "import uno" of Python 3.3 in the PyUnicode_InternInPlace function. I've done some digging and posted more information