From: Dan H. <dan...@at...> - 2010-11-16 01:45:46
|
Hi all, We have an application that we were compiling with Python 2.5 and py2exe 0.6.9. It compiled fine, and the executable ran just fine. We recently upgraded to Python 2.6. When compiling the executable, it all appears to go fine (we added the win32com.shell hack that's mentioned all over the place. However, when running the executable, it crunches away for about 2 seconds, then opens the Visual Studio debugger. It states that an unhandled exception occurred. If I open the debugger, the only useful information I get is this: Unhandled exception at 0x00402053 in ABC.exe: 0xC0000005: Access violation writing location 0xea250f1f. Any ideas as to why this is happening? I have spent many hours Googling for help, and so far nothing I have tried has made any difference. Thanks, Dan -- Dan Hensley, P.E. |
From: Massa, H. A. <ch...@gh...> - 2010-11-16 07:48:12
|
Dan, > all over the place. However, when running the executable, it crunches > away for about 2 seconds, then opens the Visual Studio debugger. It > states that an unhandled exception occurred. If I open the debugger, > the only useful information I get is this: > > Unhandled exception at 0x00402053 in ABC.exe: 0xC0000005: Access > violation writing location 0xea250f1f. > > Any ideas as to why this is happening? I have spent many hours > Googling for help, and so far nothing I have tried has made any difference. > > please check the py2exe output concerning DLLs which get "crunched" into the loader. A reason for this crash may be some dlls wrongfully included within the .exe; likely candidates are OCI.dlls and similiar. Harald -- GHUM GmbH Harald Armin Massa Spielberger Straße 49 70435 Stuttgart 0173/9409607 Amtsgericht Stuttgart, HRB 734971 - persuadere. et programmare |
From: Dan H. <dan...@at...> - 2010-11-16 16:44:30
|
Harald, Massa, Harald Armin wrote, On 11/16/2010 12:20 AM: > Dan, > > all over the place. However, when running the executable, it crunches > away for about 2 seconds, then opens the Visual Studio debugger. It > states that an unhandled exception occurred. If I open the debugger, > the only useful information I get is this: > > Unhandled exception at 0x00402053 in ABC.exe: 0xC0000005: Access > violation writing location 0xea250f1f. > > Any ideas as to why this is happening? I have spent many hours > Googling for help, and so far nothing I have tried has made any > difference. > > please check the py2exe output concerning DLLs which get "crunched" > into the loader. > > A reason for this crash may be some dlls wrongfully included within > the .exe; likely candidates are OCI.dlls and similiar. Thanks for the help. It appears that the only DLLs included are the necessary ones: python26, pythoncom26, pywintypes26, QtCore4, QtQui4, and MSVCP90. I have tracked the problem down to what I use for the 'bundle_files' option. In Python 2.5 I was using 1 to lump everything into the .exe. Now if I use 1 or 2, I get the crash. But if I use 3, the executable works properly. So it appears that this option is no longer working correctly in Python 2.6 and PyExe 0.6.9. I have found links to others with similar problems, but no solutions. I have also found PyInstaller. I think I will try that next. Thanks, Dan -- Dan Hensley, P.E. |