[pywin32-bugs] [ pywin32-Bugs-1003415 ] Access violation in call to CoInitializeSecurity
OLD project page for the Python extensions for Windows
Brought to you by:
mhammond
From: SourceForge.net <no...@so...> - 2004-08-04 17:21:19
|
Bugs item #1003415, was opened at 2004-08-04 09:21 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1003415&group_id=78018 Category: com Group: None Status: Open Resolution: None Priority: 5 Submitted By: Greg Chapman (glchapman) Assigned to: Nobody/Anonymous (nobody) Summary: Access violation in call to CoInitializeSecurity Initial Comment: I'm using pywin32 build 202 and Python 2.3.4. This call: pythoncom.CoInitializeSecurity(None, None, None, pythoncom.RPC_C_AUTHN_LEVEL_CONNECT, pythoncom.RPC_C_IMP_LEVEL_IMPERSONATE, None, 0, None) results in an access violation. Tracing through the call in a debugger, the problem is with the return from pythoncom_CoInitializeSecurity: the stack has apparently been corrupted so the function attempts to return to a NULL address. I believe the problem is in the declaration of the mypfn function pointer. Shouldn't there be a some sort of stdcall or WINAPI notation? I think both caller and callee of mypfn are popping the stack. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1003415&group_id=78018 |