Bugs item #740417, was opened at 2003-05-20 22:31
Message generated for change (Comment added) made by mhammond
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=740417&group_id=78018
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Max Shiyanovsky (shiyanovsky)
Assigned to: Nobody/Anonymous (nobody)
Summary: Potential error concealment in COM server initialization
Initial Comment:
file win32com\server\policy.py
class BasicWrapPolicy:
def _CreateInstance_(self, clsid, reqIID)
this function brings some danger in case of
win32api.error raise from server initialization routine.
I'd suggest to move except statement some rows above to
except only CLSID/PythonCom key reading failure.
----------------------------------------------------------------------
>Comment By: Mark Hammond (mhammond)
Date: 2003-05-27 12:01
Message:
Logged In: YES
user_id=14198
I don't quite follow this. Object creation should be in the
code:
if dispatcher:
retObj = dispatcher(policy, None)
else:
retObj = policy(None)
return retObj._CreateInstance_(clsid, reqIID)
And this is not wrapped in an except handler. I guess that
getting the dispatcher class could fail, but that seems alot
less likely than the class constructor failing.
Can you please give me a real example of what could fail?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=740417&group_id=78018
|