A
Alex G
Please excuse my ignorance...
I'm more of the sys admin type, not a developer. I've got an
Outlook COM Add-in developed by someone else, no access to the
source code. I need some way to get an insight into why Outlook
2002 crashes when this add-in is loaded. The crash happens just
after I close Outlook, and only if the COM add-in is loaded. In
case you are curious, the specific error message says:
The instruction at "0xADDRESS" referenced memory at "0xADDRESS".
The memory could not be "read".'
Either way, I'm looking for some sort of debugging tool to help
me figure out what's going on. I've never debugged a COM add-in,
and I'm not quite sure if it can be done when there's no access to
the source code. So I need something like the API monitor tool
from the Win2k Resource kit. API Monitor doesn't work on Win XP,
however. Anyone know of any good debugging tools? I might need
something that goes beyond ntfilemon and regmon from Sysinternals.
Oh, while I'm at it... Is it normal for a COM Add-in to register
it's classes when it's added to Outlook, rather then during
installation?
What I mean by that is that this COM add-in installs itself
seemingly without registring any classes. Then when I go into
Outlook and I add the COM add-in through the Add-in manager, I see
that it registers a few classes under HKEY_CLASSES_ROOT and
HKEY_CLASSES_ROOT\CLSID. Is that normal? You can ignore this
last question if it doesn't make sense.
Thanks!
I'm more of the sys admin type, not a developer. I've got an
Outlook COM Add-in developed by someone else, no access to the
source code. I need some way to get an insight into why Outlook
2002 crashes when this add-in is loaded. The crash happens just
after I close Outlook, and only if the COM add-in is loaded. In
case you are curious, the specific error message says:
The instruction at "0xADDRESS" referenced memory at "0xADDRESS".
The memory could not be "read".'
Either way, I'm looking for some sort of debugging tool to help
me figure out what's going on. I've never debugged a COM add-in,
and I'm not quite sure if it can be done when there's no access to
the source code. So I need something like the API monitor tool
from the Win2k Resource kit. API Monitor doesn't work on Win XP,
however. Anyone know of any good debugging tools? I might need
something that goes beyond ntfilemon and regmon from Sysinternals.
Oh, while I'm at it... Is it normal for a COM Add-in to register
it's classes when it's added to Outlook, rather then during
installation?
What I mean by that is that this COM add-in installs itself
seemingly without registring any classes. Then when I go into
Outlook and I add the COM add-in through the Add-in manager, I see
that it registers a few classes under HKEY_CLASSES_ROOT and
HKEY_CLASSES_ROOT\CLSID. Is that normal? You can ignore this
last question if it doesn't make sense.
Thanks!