Menu
▾
▴
[Oorexx-bugs] [ oorexx-Bugs-1563547 ] Possible null pointer access in OLEObject
|
From: SourceForge.net <no...@so...> - 2006-09-22 14:49:47
|
Bugs item #1563547, was opened at 2006-09-22 08:45 Message generated for change (Comment added) made by miesfeld You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1563547&group_id=119701 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Classes Group: v3.1 Status: Open Resolution: None Priority: 5 Submitted By: Mark Miesfeld (miesfeld) >Assigned to: Nobody/Anonymous (nobody) Summary: Possible null pointer access in OLEObject Initial Comment: This is in v3.1, but exists in all prior versions. When .OLEObject~new is called with the optional second parameter (either "WITHEVENTS" or "NOEVENTS") the code to search for and activate event handling assumes that pTypeInfo is valid. This is not true, it is entirely possible that pTypeInfo is null. This does no harm unless the OLE Object supports the IConnectionPointContainer interface, in which case ooRexx crashes. I ran into this twice yesterday, so it is probably not that rare of a case. The attached patch fixes this. Note that the current implementation of .OLEObject will only support events if the OLE Object being proxied supplies a Type Library. There is no real reason for ooRexx to be this restrictive, so I am going to open a feature request to change the design. ---------------------------------------------------------------------- >Comment By: Mark Miesfeld (miesfeld) Date: 2006-09-22 08:49 Message: Logged In: YES user_id=191588 Accidently assigned this to orexx, which is not what I intended. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1563547&group_id=119701 |