[issue17260] Seg fault when calling unicode() on old style object in virtualenv

Ned Deily added the comment: Duh! Issue16839 "segmentation fault when unicode(classic_class_instance)" That was recently fixed and will be available in the upcoming 2.7.4 maintenance release. -- resolution: -> duplicate stage: -> committed/rejected status: open -> closed superseder:

[issue17260] Seg fault when calling unicode() on old style object in virtualenv

Ned Deily added the comment: I can reproduce the segfault with a v2.7.3 Python + virtualenv but not with a current 2.7 tip Python + virtualenv. Nothing comes to mind immediately; I'll try bisecting. -- nosy: +ned.deily ___ Python tracker

[issue17260] Seg fault when calling unicode() on old style object in virtualenv

Johannes added the comment: Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_INVALID_ADDRESS at address: 0x0008 0x00010004e221 in PyObject_GetAttr () (gdb) bt #0 0x00010004e221 in PyObject_GetAttr () #1 0x00010004e0ff in PyObject_Unicode () #

[issue17260] Seg fault when calling unicode() on old style object in virtualenv

Antoine Pitrou added the comment: Can you please post a gdb traceback? -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list ma

[issue17260] Seg fault when calling unicode() on old style object in virtualenv

Changes by Johannes : -- title: Seg fault when calling unicode() on old style class in virtualenv -> Seg fault when calling unicode() on old style object in virtualenv ___ Python tracker __