[issue14822] Build unusable when compiled for Win 64-bit release

Jason R. Coombs added the comment: I tested against the latest tip and the issue no longer exists. -- resolution: -> works for me status: open -> closed ___ Python tracker ___

[issue14822] Build unusable when compiled for Win 64-bit release

Kristján Valur Jónsson added the comment: I am unable to reproduce. Do you have a callastack? -- nosy: +kristjan.jonsson ___ Python tracker ___

[issue14822] Build unusable when compiled for Win 64-bit release

Jason R. Coombs added the comment: I'd like to, but Apple hosed my Windows partition when upgrading to OS X Lion. A minor setback, but I'll be unable to test for a while. -- ___ Python tracker ___

[issue14822] Build unusable when compiled for Win 64-bit release

Antoine Pitrou added the comment: Could you try with latest default? -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list mai

[issue14822] Build unusable when compiled for Win 64-bit release

Changes by Stefan Krah : -- nosy: +skrah ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue14822] Build unusable when compiled for Win 64-bit release

Jason R. Coombs added the comment: It seems the Win32 build is okay. Only x64 is affected. I did a debug build, and it caught the error in errors.c line 60: Unhandled exception at 0x1e289aeb (python33_d.dll) in python_d.exe: 0xC005: Access violation reading location 0x00b8. -

[issue14822] Build unusable when compiled for Win 64-bit release

New submission from Jason R. Coombs : It appears that sometime between 64b695a6cc3d and cdcc816dea85, the Windows x64 Release build is no longer viable. It crashes when invoking the importer. -- components: Build, Windows messages: 160782 nosy: jason.coombs priority: normal severity: no