[pywin32-bugs] [ pywin32-Bugs-2496107 ] crash on File -> Open... (build 212)
OLD project page for the Python extensions for Windows
Brought to you by:
mhammond
From: SourceForge.net <no...@so...> - 2009-01-09 17:07:56
|
Bugs item #2496107, was opened at 2009-01-09 17:04 Message generated for change (Comment added) made by aminusfu You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2496107&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: pythonwin Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Robert Brewer (aminusfu) Assigned to: Nobody/Anonymous (nobody) Summary: crash on File -> Open... (build 212) Initial Comment: I just upgraded from Python 2.5 to 2.6.1 (I had also been using 2.6b2), and installed pywin32 build 212 for py2.6. At first, I elected not to Register Extensions, but then after some errors in Pythonwin (looking for some files in my Python25 dir and some in my Python26 dir), I re-ran the installer and changed it to Register Extensions. Ditto for Python 2.6--I made it the default Python. I'm on Vista (with most of the Avalon crap disabled). Now, when I start Pythonwin.exe, and click either the "Open" toolbar button or select "File...Open" from the menu, Pythonwin immediately crashes without even showing the file selection dialog. Debug info: Unhandled exception at 0x1e006c6d in Pythonwin.exe: 0xC0000005: Access violation reading location 0x00000004. VS2003 jumped to "void * __cdecl _heap_alloc_base (size_t size)" in malloc.c. Here's the call stack: python26.dll!1e006c6d() win32ui.pyd!1e2bfc70() win32ui.pyd!030031a8() ntdll.dll!7756878a() ntdll.dll!7752ec7e() ntdll.dll!77562d96() ntdll.dll!7752ec63() > msvcr71.dll!_heap_alloc(unsigned int size=2002134087) Line 212 + 0x5 C ntdll.dll!7756240b() ntdll.dll!77562054() ntdll.dll!77562033() ntdll.dll!77561843() ntdll.dll!7756240b() ntdll.dll!77562447() ntdll.dll!7753c4d1() ntdll.dll!77562054() ntdll.dll!77562033() ntdll.dll!7753c652() ntdll.dll!7756214c() ntdll.dll!7756523f() ntdll.dll!77565244() ntdll.dll!77562033() ntdll.dll!77561c21() ntdll.dll!7756526c() advapi32.dll!76180f7a() advapi32.dll!76180efc() advapi32.dll!76196578() advapi32.dll!76196578() advapi32.dll!76196578() mfc71.dll!7c1de203() win32ui.pyd!03003212() win32ui.pyd!0300349d() win32ui.pyd!0303f31b() python25.dll!027af402() python25.dll!027b0989() python25.dll!0272a83d() python25.dll!027c3217() python25.dll!0272c1f2() python25.dll!02752966() python25.dll!027aed07() python25.dll!027544a5() python25.dll!0276cf6a() python25.dll!0276cfa6() python25.dll!0276abdf() python25.dll!0277e137() python25.dll!0272ad92() python25.dll!0272cdca() python25.dll!0276090e() python25.dll!02729b9e() python25.dll!0272ae02() python25.dll!0272c5c1() python25.dll!0272cdca() python25.dll!0276090e() python25.dll!0272dcdd() python25.dll!0272dd42() python25.dll!02769b22() python25.dll!027dc52a() python25.dll!0277e137() python25.dll!027166dc() python25.dll!02716786() python25.dll!02716928() python25.dll!0276bcb9() python25.dll!0276be07() python25.dll!027512d8() python25.dll!027cbb8d() python25.dll!02752680() python25.dll!027525c3() python25.dll!02752966() python25.dll!0276c466() python25.dll!0276c499() python25.dll!0276c7ee() ntdll.dll!77561843() ntdll.dll!775616dc() ntdll.dll!77562033() ntdll.dll!77561843() kernel32.dll!771e7a7e() msvcr71.dll!_heap_alloc(unsigned int size=45944068) Line 212 C msvcr71.dll!_heap_alloc(unsigned int size=) Line 212 + 0x5 C Why would pythonwin for 2.6 be calling python25.dll? Sadly, I'm not the C debugger I used to be (and don't have the patience for a debug build of Python), but I notice the "original symbol location" for the python25.dll is "c:\trentm\as\ActivePython-devel\build\py2_5_1-win32-x86-apy25-rrun\python\PCbuild\python25.pdb" and for win32ui.pyd just above that, it's "O:\src\pywin32\build\temp.win32-2.5\Release\win32ui.pdb". The calls above that seem to be OK. ---------------------------------------------------------------------- >Comment By: Robert Brewer (aminusfu) Date: 2009-01-09 17:07 Message: By the way, I can open a file into Pythonwin by right-click, "Edit with Pythonwin". Choosing a recent file works too, e.g.: "File -> 1. threading.py". But the Open button still crashes. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2496107&group_id=78018 |