Incorrect Type Name references in defaultvis.natvis visualizers for standard library - by mloskot

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


2
0
Sign in
to vote
ID 705993 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 11/18/2011 6:37:29 PM
Access Restriction Public
Moderator Decision Sent to Engineering Team for consideration

Description

The new style visualizers defined in
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\Packages\Debugger\Visualizers\defaultvis.natvis
for elements of the C++ Standard Library have incorrectly defined Type Name attributes.
These definitions refer to std::tr1 whereas the types in Visual Studio 11 are now defined in std:: but not aliased from std::tr1 as it is in Visual Studio 2010.

So, for instance

<Type Name="std::tr1::shared_ptr&lt;*&gt;">

should read

<Type Name="std::shared_ptr&lt;*&gt;">

The incorrect references to std::tr1:: lead to lack of proper visualization while debugging.
Sign in to post a comment.
Posted by Microsoft on 4/29/2014 at 12:24 PM
Thank you for reporting this issue. This issue has been fixed in Visual Studio 2013. You can install a trial version of Visual Studio 2013 with the fix from: http://go.microsoft.com/?linkid=9832436
Posted by Microsoft on 3/1/2012 at 6:37 PM
Hi,

Thanks for reporting this bug. We've fixed it, and the fix will be available in VC11.

The fix went beyond dealing with the std::tr1 => std change. I audited all of the STL's visualizers, for both the old and new engines (the new engine is used by default, reads stl.natvis, and is very robust - while the old engine is used for Edit And Continue and reads autoexp.dat), and fixed various problems that had accumulated during VC11's development. For example, we changed how the STL's iterators work, which affected the visualizers.

As a bonus, an expired weak_ptr now reveals its weak refcount (keeping the control block alive).

If you have any further questions, feel free to E-mail me at stl@microsoft.com .

Stephan T. Lavavej
Visual C++ Libraries Developer
Posted by MS-Moderator07 [Feedback Moderator] on 11/20/2011 at 10:22 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by mloskot on 11/18/2011 at 7:10 PM
I have just attached screenshot (vs11-visualizers-broken-2.png) presenting the broken visualization. Hopefully it will get attached here.
Posted by MS-Moderator01 on 11/18/2011 at 6:52 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)