microsoft / microsoft/vscode-cpptools
NATVIS files specified in the launch configuration are not refreshed/reloaded on change
Open
Nobody has claimed this yet.
debugger
Feature Request
- 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 22H2
- VS Code: 1.74.2
- C/C++ extension: 1.13.8
Bug Summary and Steps to Reproduce
Bug Summary:
Visualizer files associated with a Visual Studio project benefit from automatic reloading on change. This is generally critical to author new visualizations without engaging in an expensive stop/start iteration loop.
Steps to reproduce:
- Launch any configuration with an associated visualizer file
- Author changes to the NATVIS file
- Observe that the NATVIS file is not reparsed or reloaded by the debugger runtime
Debugger Configurations
Any configuration with a `visualizerFile` specified reproduces the issue.
Debugger Logs
No relevant logs were produced with the engine and trace 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
Start by reproducing the issue with a launch configuration that specifies visualizerFile, then trace how the C/C++ extension handles that configuration and NATVIS changes. Done means edits to the associated NATVIS file are reparsed or reloaded by the debugger without stopping and restarting the session.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, typescript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100