On Feb 28, 2008, at 5:54 PM, Mark Hammond wrote:
I am using Visual C++ 9.0 to build pywin32, and Dependency Walker showsthat the pyhon.exe from the 2.6 snapshot is linked against the Visual C++ 9.0 runtime.Ahh - sorry, I missed that you are building pywin32 yourself.The installer that you provided crashes for me in the same way.Perhaps it's a bug in Python or something wrong with my machine? Otherinstallers that I have made today for Python 2.6 have succeeded. Very curious.Yes, strange. The creation of the .pyc files is done by the installer exe and it will be *that* runtime which is of interest - but depends shows theinstaller exe links against msvcr90.dll which is what we want. I'msurprised a version you build yourself does that though, as I don't believethe skeleton executable has been updated in the python core yet. Thatinstaller binary works for me (at least, it doesn't crash - but it does give a useless error message at the end ("*** run_installscript: internal error0xFFFFFFFF ***"). *sob*IIRC, building python and pywin32 from source - even the release versions -should give .pdb files which are useful for debugging. Have you tried breaking into the process using the debugger?
Yes, and it showed the crash happening in a call to realloc(). The call stack seemed oddly short, so I may have been looking at the wrong thread or something like that. I did not give it a lot of attention at the time, but I can look into it more tomorrow (in about 14 hours). Thanks for the feedback.
-Patrick -- Patrick L. Hartling Senior Software Engineer, Priority 5 http://www.priority5.com/
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ python-win32 mailing list python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32