Unable to debug x64 COM dll on VS2010 on Win7, the dll is not listed in the Module window

Question

I am not able to debug the x64 COM dll on VS 2010 and windows 7. The COM component is used by a x64 .Net application written by C#. 

The break points are never hit. I thought it might be the issue of symbol file not found. But when I went to the Debug/Window/Modules window, the COM dll was not listed (but Kernel32.dll, MFC90.dll, etc. were listed).  In ProcessExplorer, the COM dll can be seen in the modules list. 

The COM dll  and .Net application is just upgraded from 32bit and windows xp. I used to debug it.

Any idea about this issue? How does VS display modules on the Modules window? 

Thanks a lot in advance. 

Answer 1

>I am not able to debug the x64 COM dll on VS 2010 and windows 7. The COM component is used by a x64 .Net application written by C#. 

Ensure you have the debugger setting to allow mixed native & managed
code debugging.

Dave

Answer 2

No, the mixed mode is not supported when debugging x64 process. So I selected the Native mode.

What I don't understand is that why there are a lot of native dlls in the modules list while the COM dll is not. 

What are  the rules for the debugger to decide which module should be in the module list? If you compare the module list between ProcessExplorer and VS, you would find these two are not the same.

Answer 3

No, the mixed mode is not supported when debugging x64 process. So I selected the Native mode.
What I don't understand is that why there are a lot of native dlls in the modules list while the COM dll is not. 

I don't know either.

Dave

Answer 4

I'm not good at COM programming, so can you help me create a demo COM project, maybe you can share all the necessary project through the skydrive. So that we can try to research how to debug into the code for this special method calling.

---

Mike Zhang[MSFT]
MSDN Community Support | Feedback to us