Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot inspect a std::wstring variable (node-gyp + Windows 10) #319

Closed
antropit opened this issue Jun 2, 2020 · 6 comments
Closed

Cannot inspect a std::wstring variable (node-gyp + Windows 10) #319

antropit opened this issue Jun 2, 2020 · 6 comments

Comments

@antropit
Copy link

antropit commented Jun 2, 2020

OS: Microsoft Windows 10.0.18362.836
VSCode version: 1.45.1
Extension version: 1.5.2
Toolchain version: node-gyp@5.0.7 + VS2017 (15.9.28307.1000) + MSBuild 15.9.21.664
Build target: Platform=x64
Python version: using Python version 2.7.16

I got "error: summary string parsing error" on all my std::wstring variables when inspecting them in VSCode. I post a question and decided to post a copy here.

Also, I try to change expression evaluator in launch.json with python option tooltip not showing at all, but others to show the same error as in the image. Side panel with scopes in all cases shows the same error.

@longnguyen2004
Copy link

What C++ STL are you using? Microsoft STL, libstdc++ or libc++?

@antropit
Copy link
Author

antropit commented Jun 2, 2020

I think MSBuild can use only Microsoft STL. I don't see any tags in my autogenerated by node-gyp .vcxproj that would indicate otherwise.

@vadimcn
Copy link
Owner

vadimcn commented Jun 2, 2020

LLDB's STL visualizers support libstdc++ and libc++, but not Microsoft's implementation, as far as I know. Probably still tries to apply them, but fails.

@antropit
Copy link
Author

antropit commented Jun 3, 2020

It sounds like I must close an issue here. Thanks.

@antropit antropit closed this as completed Jun 3, 2020
@vadimcn
Copy link
Owner

vadimcn commented Jun 3, 2020

If you feel like it, you can try to create the debug visualizers yourself: https://lldb.llvm.org/use/variable.html. This example may be a good starting point.

@antropit
Copy link
Author

antropit commented Jun 3, 2020

Thanks a lot, but not now) I’d better send a request to their Bugzilla.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants