Win2k and Python access violation
Win2k and Python access violation - please help me out here!
Jason Maskell backov at nospam.csolve.netFri Feb 25 14:01:35 EST 2000
- Previous message (by thread): Win2k and Python access violation - please help me out here!
- Next message (by thread): Win2k and Python access violation - please help me out here!
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
gmcm at hypernet.com (Gordon McMillan) wrote in <1260623840-9876921 @hypernet.com>: >Jason wrote: > >> Oops, I missed 3 lines at the top of the call stack: >> >> NTDLL! 77f8ed61() >> NTDLL! 77f8ecf1() >> MSVCRTD! 10238575() > >Are you using python15.dll or python15_d.dll? Mixing run time >libraries is a great way to crash. Using the debug dll. Just for fun, I changed over to the release version and compiled it. Same problem. The release side is using all release dlls. Cheers, Jason
- Previous message (by thread): Win2k and Python access violation - please help me out here!
- Next message (by thread): Win2k and Python access violation - please help me out here!
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list