Natvis: Template parameter mismatch - by Jean Geffroy

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.

Sign in
to vote
ID 767225 Comments
Status Closed Workarounds
Type Bug Repros 3
Opened 10/12/2012 10:34:18 AM
Access Restriction Public


I am currently working on a project which uses STLPort and I want to create a Natvis file so that we can easily debug STL containers. I am however facing a problem with some containers: the template parameters $Tn defined in the natvis file are not properly resolved, except for the very first element that is observed through the debugger within the currently active debugging session.

This is a very important issue for us, since not being able to properly debug STL types with VS2012 slows down the team.
Sign in to post a comment.
Posted by Microsoft on 4/29/2014 at 12:31 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:
Posted by sébastien Wybo on 5/22/2013 at 12:58 AM
Has this issue been fixed in one of the VS2012 updates? Because I'm having a similar problem with Qt 4.8 types when using nested, different template parameters, types.
Posted by Microsoft on 12/18/2012 at 5:24 PM
Thank you for your feedback. We have determined that the problem in question is indeed a bug in our handling of natvis files and are considering fixing this for a future release. In the meantime, you should know that the bug gets triggered when you have a natvis entry for a template class that uses a node type which is not a template class. Given this, you may be able to work around the issue by changing the code so that the tree node is a template class which inherits the parent object's template parameters, rather than a non-template class, requiring $T3 to bind to the 3rd parameter type of the parent object. - Visual Studio Debugger Team
Posted by Microsoft on 10/15/2012 at 1:00 AM
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 Microsoft on 10/12/2012 at 10: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(