rwilson032697
asked on
Debugging COM objects...
Hi All,
I have an annoying problem trying to debug a COM object implemented in a DLL.
In the DLL delphi project I can set the host application and then run the EXE/DLL - the application runs and creates an instance of the COM object using CreateCOMObject (with the appropriate GUID).
However, Delphi does not stop on any of the breakpoints I set in the code. I have verified that the code is in fact running (added a message etc), so I am quite confused as to why it does not break!
I have had no difficulties debugging into ordinary DLLs, but this COM object in DLL doesn't want to play ball ;-(
Does anyone have tips on how they debug their in-process COM objects?
Cheers,
Raymond.
I have an annoying problem trying to debug a COM object implemented in a DLL.
In the DLL delphi project I can set the host application and then run the EXE/DLL - the application runs and creates an instance of the COM object using CreateCOMObject (with the appropriate GUID).
However, Delphi does not stop on any of the breakpoints I set in the code. I have verified that the code is in fact running (added a message etc), so I am quite confused as to why it does not break!
I have had no difficulties debugging into ordinary DLLs, but this COM object in DLL doesn't want to play ball ;-(
Does anyone have tips on how they debug their in-process COM objects?
Cheers,
Raymond.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
No problem.
However, I was unable to determine if you got the problem fixed from your last post.
You can also try placing the COM object in the same project group as the host application. Build all projects to rebuild the symbol tables and try debugging it again.
Hope this helps.
Regards,
Rob
However, I was unable to determine if you got the problem fixed from your last post.
You can also try placing the COM object in the same project group as the host application. Build all projects to rebuild the symbol tables and try debugging it again.
Hope this helps.
Regards,
Rob
ASKER
Ho - it is still an existing problem, but one I won't be revisiting until I need to visit that particular dungeon again.
What the hell - you've been the only person to even reply so you deserve the points just for the D7 tips! :-)
Cheers,
Raymond.
What the hell - you've been the only person to even reply so you deserve the points just for the D7 tips! :-)
Cheers,
Raymond.
Thank you very much Raymond.
I hope you find the answer your looking for. I'll keep my eye on this topic in the event you visit that particular dungeon again. :)
Regards,
Rob
I hope you find the answer your looking for. I'll keep my eye on this topic in the event you visit that particular dungeon again. :)
Regards,
Rob
ASKER
Thanks for the tip wrt Delphi 7 - I like the sound of teh cross process step into support! Currently we are using D6 but will upgrade soon (hopefully :-)
It's a perplexing problem all right, and annoying because you end up having to rely on logging to see what is happening. I suspect it may be a subtle conflict or misconfiguration when the OS goes looking for an active instance of the COM server...
Cheers,
Raymond.