microsoft / microsoft/vscode-cpptools
Natvis files embedded in PDBs produced using `/NATVIS:[file]` are not activated by the debugger
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Environment
- OS and Version: Windows 10 Pro 21H1
- VS Code Version: 1.73.1 (user setup)
- C/C++ Extension Version: 1.13.4 (Pre-Release)
- Other extensions you installed: Reproduces without other extensions installed
Bug Summary and Steps to Reproduce
Produce any DLL or executable with a link command, supplying the /NATVIS command line argument as documented here. Unlike the natvis file supplied in the launch settings, natvis files embedded in PDBs in this way are not recognized.
Debugger Configurations
No specific launch or task configuration is needed.
Debugger Logs
No relevant logs are produced with trace and engine logging enabled.
Other Extensions
No response
Additional Information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue by building a DLL or executable with the link command's /NATVIS:[file] option, then launch it through the C/C++ extension debugger. Compare that behavior with a natvis file supplied in launch settings. Done means the debugger recognizes and applies Natvis files embedded in the PDB, with appropriate coverage for the reported configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100