Sign in to follow this  

VS 2015 debugger not able to show string content

This topic is 821 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hello!

 

    Not long ago I switched from Visual Studio 2013 to new Visual Studio 2015. Everything went good, compiling and working on it, is much faster then before. Few new diagnostic tools, great! But... I have ugly problem which destroys everything. When I run my problem with debuger, breaks somwhere in the code, and try to look on my string variable, I can't see it's content. Instead of it, I see npos value=4294967295 and two (error) = 0. Other types of variables, even from my class works fine. Does anyone have same problem or know how to fix it? 

 

 

Thanks!

Share this post


Link to post
Share on other sites
Are you debugging a release or otherwise optimized version of your program? Optimizations can make it hard for debuggers to find variables in memory (assuming they haven't been removed entirely or their memory re-used by another variable whose lifetime doesn't overlap)

Share this post


Link to post
Share on other sites

Are you debugging a release or otherwise optimized version of your program? Optimizations can make it hard for debuggers to find variables in memory (assuming they haven't been removed entirely or their memory re-used by another variable whose lifetime doesn't overlap)

 

No, i use proper (not modified, setup from installation) debug compilation. Even when I create new project with simple "Hello World" variable it doesn't work...

Edited by Delli

Share this post


Link to post
Share on other sites
Do you have a screenshot of the bug? I can't figure out what might be wrong from the OP's description. (And don't have a copy of 2015 on me to test right now)

If Oberon is correct and it's restricted to wstring then my guess is going to be that the debugger either isn't displaying multi-byte characters correctly, or it's using standard chars for storage and trying to display a multi-byte string as a 8-bit string. Though I would imagine that VS would ship with a visualizer that handled that...

Edit: I almost forgot - are you debugging a purely native app? (No /clr flag, no mixed-mode debugging, no C++/CX or C++/CLI) Some of VS's visualizers only work in pure native mode only. Edited by SmkViper

Share this post


Link to post
Share on other sites

Microsoft Connect is the proper place to raise these issues, as that will get you feedback from Microsoft itself, and also get a bug logged in their tracker in case something is genuinely wrong with VS and needs to be fixed in their code.


That too. I'll be damned if I could figure out how to search the site for existing reported issues though... I usually have to go through a link someone posts on stackoverflow.

Share this post


Link to post
Share on other sites

This topic is 821 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this