debugging in-proc COM server with out-of-proc COM server and COM client

debugging in-proc COM server with out-of-proc COM server and COM client

Post by aevans110 » Mon, 15 Dec 2003 03:50:12


Greetings

I have written two COM servers in ATL/BCB and a COM client in VB. The
out-of-process COM server is a client to the in-process COM server.
The VB COM client is a client to the out-of-process COM server.

--------------------
| ---------------- | ------------
| | COM Server DLL | |______| COM Client |
| ---------------- | | (VB) |
| COM Server EXE | ------------
--------------------

I want to debug the in-process COM server, but whenever I try, all my
breakpoints go dark.

I have tried both targetting the out-of-process EXE as the de ***
process for the in-process DLL and hitting "run", as well as
instantiating an object exposed by the EXE from the VB client, then
attaching to the EXE process after the fact. Both methods give the
same result: dark breakpoints.

I can debug the out-of-process COM server just fine by itself and I
can debug in the in process COM server just fine by itself (if I
create a VB client for it).

Can anyone tell me what I'm doing wrong?

Thanks
Tony
 
 
 

debugging in-proc COM server with out-of-proc COM server and COM client

Post by aevans110 » Mon, 15 Dec 2003 03:54:42

Greetings

I have written two COM servers in ATL/BCB and a COM client in VB. The
out-of-process COM server is a client to the in-process COM server.
The VB COM client is a client to the out-of-process COM server.

--------------------
| ---------------- | ------------
| | COM Server DLL | |______| COM Client |
| ---------------- | | (VB) |
| COM Server EXE | ------------
--------------------

I want to debug the in-process COM server, but whenever I try, all my
breakpoints go dark.

I have tried both targetting the out-of-process EXE as the de ***
process for the in-process DLL and hitting "run", as well as
instantiating an object exposed by the EXE from the VB client, then
attaching to the EXE process after the fact. Both methods give the
same result: dark breakpoints.

I can debug the out-of-process COM server just fine by itself and I
can debug in the in process COM server just fine by itself (if I
create a VB client for it).

Can anyone tell me what I'm doing wrong?

Thanks
Tony

 
 
 

debugging in-proc COM server with out-of-proc COM server and COM client

Post by aevans110 » Tue, 16 Dec 2003 10:40:20

I should also tell you that I'm running C++ Builder 6.0 with the
4th(?) Service Pack (Build 10.166) under W2KASSP4.

Also, sorry for the double post of the original message. My cheap ISP
discontinued NNTP, so I'm now using confusing Google to post.

Thanks
Tony