WatchWindow incorrectly calculates member address - by Debugini

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 800920 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 9/16/2013 3:28:09 AM
Access Restriction Public


In C++, when I use the context menu command "Add Watch" for a perfectly displayed member variable further up in the inheritance, the VisualStudio generates an expression into the watch window which it then is unable to resolve correctly.

Verified to be broken in VS 2013 Preview and RC.
Sign in to post a comment.
Posted by Debugini on 9/11/2014 at 5:12 AM
Thanks for fixing this issue! Does this fix also address the same problem in evaluation of conditional breakpoints (when using the the watch expression as basis for the condition)?
Posted by Microsoft on 9/10/2014 at 4:27 PM
Thanks for reporting this issue, and sorry for the delay in response. We have successfully fixed it for Visual Studio "14" and the upcoming update to Visual Studio 2013. Unfortunately, as you noted, we made the fix too recently for it to go into CTP 3 of Visual Studio "14". You should see the problem fixed in future ctp's, starting about a month from now.
Posted by Debugini on 8/18/2014 at 12:36 PM
Still broken in VS "14" CTP3
Posted by Debugini on 6/11/2014 at 3:53 AM
The bug is still present in Visual Studio "14" CTP.
Posted by Microsoft on 9/17/2013 at 5:45 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 9/16/2013 at 3:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(