Debugger behavior for ATL COM objects with connection points - by Bill Block

Status : 

  Deferred<br /><br />
		The product team has reviewed this issue and has deferred it for consideration at a later time.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 790263 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 6/16/2013 5:57:57 AM
Access Restriction Public


I have attached a solution and Word document that illustrates the problem.  In the AtlProject1 are two classes: 

• CTestClass1—no connection points
• CTestClass2—contains connection points

When debugging the application, I can drill down into the CTestClass1 instance via its smart pointer and examine variables, but I cannot do so for the CTestClass2 instance that contains connection points. 

Here is the informatioin on the developement system:

Microsoft Visual Studio Professional 2012
Version 11.0.60315.01 Update 2
Microsoft .NET Framework
Version 4.5.50709

Installed Version: Professional

Sign in to post a comment.
Posted by Martin Bauer on 8/12/2013 at 12:18 AM
I have the same problem with an ATL COM object (Dll-Project) without connection point when I use the object in a C++ native client project.
When I use a C# .NET client project all works fine !?

I use VS 2012 Update 3.

Is the problem already known?

When can you release a fix of this bug?
Posted by Microsoft on 6/24/2013 at 3:09 PM
Thank you for reporting this issue. The behaviour you are seeing is due to a shortcoming in the way the VS debugger decodes object virtual function tables. We have taken note of the issue and will consider fixing it in a future release of Visual Studio.

VC++ Compiler Team.
Posted by Microsoft on 6/17/2013 at 1:27 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 6/16/2013 at 6:51 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(