Instructions
Install it via using the Extensions view in VS Code or download a vsix that matches your OS from Assets section below (or the "Download" dropdown in the "Version History" tab section on the Marketplace website) and then use the Extensions: Install from VSIX...
command in VS Code (don't double-click the .vsix or another app like VS might try to open it incorrectly).
Requirements
- VS Code 1.63.0 or later.
Changes
Bug Fixes
- Fix an issue with extension activation failing if
C_Cpp.intelliSenseEngine
was set toDisabled
. #9083
Instructions
Install it via using the Extensions view in VS Code or download a vsix that matches your OS from Assets section below (or the "Download" dropdown in the "Version History" tab section on the Marketplace website) and then use the Extensions: Install from VSIX...
command in VS Code (don't double-click the .vsix or another app like VS might try to open it incorrectly).
Requirements
- VS Code 1.63.0 or later.
Changes
New Features
- Add debugger support for Apple M1 (osx-arm64). #7035
- Resolves issue "[Big Sur M1] ERROR: Unable to start debugging. Unexpected LLDB output from command "-exec-run". process exited with status -1 (attach failed ((os/kern) invalid argument))". #6779
- Add a build and debug button when
C_Cpp.debugShortcut
istrue
. #7497- The "Build and Debug Active File" command has been split into "Debug C++ File" and "Run C++ File", and it has been removed from the context menu.
- Add Alpine Linux arm64 support (VSIX).
- Add x64 debugger for CppVsdbg on Windows x64.
Enhancements
- Reserved identifiers with characters that match typed characters in the correct order but not contiguously are initially filtered in the auto-completion list. Doing a
ctrl
+space
in the same location will show all auto-complete suggestions. #4939 - Add
dotConfig
property to IntelliSense Configuration (c_cpp_properties.json) to use .config file created by Kconfig system.- Matheus Castello (@microhobby) PR #7845
- Rework how cancelation is processed for semantic tokens and folding operations. PR #8739
- Make SwitchHeaderSource use the
workbench.editor.revealIfOpen
setting.- Joel Smith (@joelmsmith) PR #8857
- Add tag parser error logging. #8907
- Add error and warning messages if the VSIX for an incompatible or mismatching platform or architecture is installed. #8908
- Add a "More Info" option when an incompatible VSIX is encountered. PR #8920
- Add
;
tobreak
andcontinue
completion keywords. #8932 - Prevent stripping of format specifiers from -exec commands.
- Gareth Rees (@gareth-rees) MIEngine#1277
- Improve messages for unknown breakpoints and watchpoints.
- Gareth Rees (@gareth-rees) MIEngine#1282
Bug Fixes
- Fix some IntelliSense parsing bugs. #5117
- Fix IntelliSense process crashes caused by a stack overflow on Mac. #7215, #8653
- Fix exclusions not applying during tag parsing of non-recursive dependent includes. #8702
- Fix issue that could cause an infinite loop when clicking on a preprocessor conditional directive. #8717
- Fix excludes applying to cases it should not when running code analysis. #8724
- Fix a crash when visualizing local variables for Microsoft Edge (msedge.exe) #8738
- Fix some system defines being incorrectly removed when running code analysis. #8740
- Prevent an error from being logged due to custom configuration processing prior to the provider being ready. #8752
- Fix incorrect crash recovery with multiroot. #8762
- Fix random compiler query, clang-tidy, or clang-format failure on Windows. #8764
- Fix invoking commands before cpptools is activated. #8785
- Fix a bug on Windows with semantic tokens updating. #8799
- Fix tag parser failure due to missing DLL dependencies on Windows. #8851
- Fix semantic tokens getting cleared for all other files in a TU after editing a file. #8867
- Fix a bug and typos with cppbuild task providers.
- Fix an issue that could cause the extension to fail to start up properly. PR #8906
- Fix handling of
-B
with compiler querying. #8962 - Fix incorrect "Running clang-tidy" status indications with multi-root workspaces. #8964
- Fix a crash during shutdown and potential database resetting due to shutdown being aborted too soon. PR #8969
- Fix an issue that could cause the active file to not be configured by a configuration provider when custom configurations are reset. #8974
- Fix detection of Visual Studio 2015. #8975
- Fix mingw clang being detected as gcc. #9024
- Fix a random crash on file open.
- Fix some IntelliSense crashes.
- Fix some IntelliSense parsing bugs.
- Fix a bug with IntelliSense updating not working if a file was closed and reopened while its TU was processing an update.
- Fix a potential heap corruption when
files.associations
are changed. - Update translated text.
Documentation
- Clarify how to get binaries when debugging the source from GitHub.
- Hamir Mahal (@hamirmahal) PR #8788
Note
- This release is identical to 1.9.6 (pre-release), other than being built for the "release" channel and an updated changelog.
Instructions
- Download the vsix in the Assets section which matches your OS (Alpine Linux x64 is not available until 1.9.6) and run the "Install from VSIX" command in VS Code (don't double-click the .vsix or another app like VS might try to open it incorrectly).
- Let us know if anyone is able to repro bug #9041. If it's good, then we can publish this as 1.9.6.
UPDATE: It wasn't fixed -- got a repro. I've removed the vsix's.
Requirements
- VS Code 1.63.0 or later.
Changes
Bug Fix
- Redo 1.9.4 changes with a (potential) fix for issue #9041
UPDATE: The vsix has been removed. The problem is vcmeta.dll is failing to load, possibly due to a missing dependency that ships next to cl.exe in VS 2022.
This is a debug build for Windows x64 intended to be used to get assertion failure information for bug #8851. The other changes are still going to be in 1.9.4, but built for release instead of debug. The debug build is a lot slower and may cause annoying assertion failure dialog boxes to appear so it's not recommended to be used in general. We plan to remove this Release after we've gotten the assertion info.
Instructions
- Download the cpptools-win64.vsix in the Assets section (assuming you're running Windows x64) and run the "Install from VSIX" command in VS Code (don't double-click the .vsix or another app like VS might try to open it incorrectly).
Requirements
- VS Code 1.63.0 or later.
Changes
Enhancements
- Reserved identifiers with characters that match typed characters in the correct order but not contiguously are initially filtered in the auto-completion list. Doing a
ctrl
+space
in the same location will show all auto-complete suggestions. #4939 - Show "Catastrophic error" during tag parsing with an Error logging severity and report the number of occurrences via telemetry. #9013
Bug Fixes
This has the same changes as 1.9.4-debug, but with release bits and 3 vcmeta.dll dependencies added/updated in an attempt to fix bug #8851. If it fixes the issue, we can publish this as 1.9.4.
Instructions
Install it via using the Extensions view in VS Code or download a vsix that matches your OS from the "Download" dropdown in the "Version History" tab section on the Marketplace website and then use the Extensions: Install from VSIX...
command in VS Code (don't double-click the .vsix or another app like VS might try to open it incorrectly).
Requirements
- VS Code 1.63.0 or later.
Changes
Bug Fixes
- Suppress incorrect warnings on ARM64 macOS. #8756
- Fix debugger regressions. #8760
- Remove
Offline Installation
section from README.md. #8769 - Fix performance issue with loading large PDBs. #8775
Known Issues
- Go to definition on macros in gcc mode may go to the wrong location. #8577
- Some clang-tidy errors may be incorrectly excluded. #8724
- Code analysis may not have the correct system defines. #8740
Note
- This release is also identical to 1.8.5, released at the same time, but with the vsix built for insiders.
Instructions
Install it via using the Extensions view in VS Code or download a vsix that matches your OS from the "Download" dropdown in the "Version History" tab section on the Marketplace website and then use the Extensions: Install from VSIX...
command in VS Code (don't double-click the .vsix or another app like VS might try to open it incorrectly).
Requirements
- VS Code 1.63.0 or later.
Changes
New Features
- Add data breakpoints (memory read/write interrupts) for
gdb
debugging. #1410 - Add "All Exceptions" Breakpoint for cppdbg #1800
- Add multi-threaded code analysis (using
clang-tidy
) based on the IntelliSense configuration. It defaults to using up to half the cores, but it can be changed via theC_Cpp.codeAnalysis.maxConcurrentThreads
setting. #2908. - Add support for Alpine Linux #4827
- Implement platform-specific VSIX's via the marketplace. #8152
Enhancements
- The maximum number of threads to use for Find All References can be configured with the
C_Cpp.references.maxConcurrentThreads
settings. #4036. - The IntelliSense processes launched to confirm references during Find All References can be cached via the
C_Cpp.references.maxCachedProcesses
setting. #4038 - The maximum number of IntelliSense processes can be configured with the
C_Cpp.intelliSense.maxCachedProcesses
setting, and the number of processes will automatically decrease when the free memory becomes < 256 MB and it can be configured to use less memory via themaxMemory
settings (memory usage from code analysis is not handled yet). #4811 - Switch from 32-bit to 64-bit binaries on 64-bit Windows. #7230
- Add a compiler arg to the generated gcc build task to display colored text. PR #8165
- Add
static
and other modifiers to IntelliSense hover results. #8173 - Add a configuration warning when the default compiler modifies an explicitly set
intelliSenseMode
.
Bug Fixes
- Fix several IntelliSense bugs. #5704, #6759, #8412, #8434
- Fix newlines not being handled in comments with a Doxygen tag. #5741
- Fix Doxygen comments with
\0
being truncated. #6084 - Fix
files.exclude
not working for directories external to the active workspace folder. #6877 - Fix [MSYS2 GDB 10.2] gdb: ERROR: Unable to start debugging. Unexpected GDB output from command "-exec-run". Error creating process #7706
- Fix a bug with vcFormat inserting additional spaces between
}
andelse
. #7731 - Fix GCC system include processing on Windows. #8112, #8496
- Remove redundant cl.exe from the build and debug active file configuration list. #8168
- Fix string elements to render as code in the IntelliSense configuration UI. PR #8271
- Fix IntelliSense process crash on AMD Ryzen 3000 series processors without updated drivers. #8312
- Fix bug with
wmic
not being recognized during Windows attach debugging. #8328 - Fix Go to Type Definition on pointer types. #8337
- Fix a "Cannot read property" error during deactivation if the language service wasn't fully activated. #8354
- Fix an issue in which the language id for header files were not updated to match the source file of its TU. #8381
- Fix parsing of
bit_cast
with gcc mode IntelliSense. #8434 - Fix the tag parser getting stuck on certain code. #8459
- Fix an invalid success message when a build task fails. #8467
- Fix compiler querying with certain Cygwin/MSYS2 compilers on Windows. #8496
- Fix a bug with conditional breakpoints. #8515
- Fix non-ASCII output with
cppbuild
tasks. #8518 - Fix 3 settings not getting environment variables resolved after a settings change. #8531
- Don't block running a task if it doesn't use the active file. #8586
- Fix a command not found error message after clicking the database status icon when commands aren't available. #8599
- Fix /RTC compiler checks failures don't break into debugger #8646
- Fix workspace rescanning (tag parsing) not automatically happening after c/cpp associations are added to
files.associations
. #8687 - Fix debugging when Windows binaries are linked with /PDBPageSize > 4k. #8690
- Switch usage of
-dD
to-dM
when compiler querying. #8692 - Fix breakpoints with msys2 gcc. #8696
- Fix no document symbols appearing in certain cases. #8726
- Fix an issue in which multiple (potentially different) diagnostics were delivered for headers shared by multiple TUs.
- Fix some translations.
Other
Known Issues
- Go to definition on macros in gcc mode may go to the wrong location. #8577
- Some clang-tidy errors may be incorrectly excluded. #8724
- Code analysis may not have the correct system defines. #8740
Note
- This release has the same language service components as 1.8.1 (insiders4), released 4 days earlier, but there's an updated debugger and an updated changelog.
- This release is also identical to 1.8.3, released at the same time, but with the vsix built for insiders.
Instructions
Install it via using the "Switch to Pre-Release Version" in VS Code or download a platform-specific vsix from the "Download" dropdown in the "Version History" tab in the Marketplace and then use the Extensions: Install from VSIX...
command in VS Code.
Requirements
- VS Code 1.63.0 or later.
Note: Due to new version numbering requirements for VS Code pre-release extension support, this will appear in VS Code as version
1.8.1
instead of1.8.0-insiders4
Changes
Bug Fixes
- Fix several IntelliSense bugs. #8412, #8487, #8677, #8701
- Fix code analysis with a long command line on Windows. #8560.
- Fix code analysis not correctly handling defines with
"
. #8675 - Fix
files.exclude
on workspace relative paths (e.g."folder"
). #8676 - Fix workspace rescanning (tag parsing) not automatically happening after c/cpp associations are added to
files.associations
. #8687 - Switch usage of
-dD
to-dM
when compiler querying. #8692 - Fix
�
instead of…
in logging messages. #8694. - Fix invalid define when using a custom env.variable. #8695
- Fix forced includes with code analysis. #8707
- Fix clang-tidy "notes" applying to excluded files being shown for other non-excluded files and possibly causing some warnings to not appear. #8723
- Fix no document symbols appearing in certain cases. #8276
Known Issues
Instructions
Download the .vsix that matches your OS and run the "Install from VSIX" command in VS Code (don't double-click the .vsix or another app like VS might try to open it incorrectly).
Note: Due to new version numbering requirements for VS Code pre-release extension support, this will appear in VS Code as version
1.8.0
instead of1.8.0-insiders3
Requirements
- VS Code 1.63.0 or later.
Changes
New Features
- Add "All Exceptions" Breakpoint for cppdbg #1800
- Add support for Alpine Linux #4827
- Implement platform-specific VSIX's via the marketplace. #8152
Bug Fixes
- Fix [MSYS2 GDB 10.2] gdb: ERROR: Unable to start debugging. Unexpected GDB output from command "-exec-run". Error creating process #7706
- Remove redundant cl.exe from the build and debug active file configuration list. #8168
- Stop adding
-fms-extensions
by default for gcc-based compilers on Windows. #8475, #8487 - Fix clang-tidy header warnings sometimes not disappearing after the issue is fixed. #8502
- Fix clang-tidy processing status indicator getting stuck after editing/saving a header that is currently being analyzed by clang-tidy. #8504
- Fix non-ASCII output with
cppbuild
tasks. #8518 - Fix 3 settings not getting environment variables resolved after a settings change. #8531
- Fixes to translations. #8536
- Fix /RTC compiler checks failures don't break into debugger #8646
Instructions
To use the "offline" .vsix (that doesn't download OS-based dependencies on extension activation), download the .vsix that matches your OS and run the "Install from VSIX" command in VS Code (don't double-click the .vsix or another app like VS might try to open it incorrectly).
Requirements
- VS Code 1.60.0 or later.
Changes
Bug Fixes
- Fix GCC system include processing on Windows. #8112, #8496
- Fix the tag parser getting stuck on certain code. #8459
- Fix
C_Cpp.codeAnalysis.maxConcurrentThreads
using the wrong value. #8471 - Fix save failing after editing a header that is used by clang-tidy for a TU that is different from the default TU. #8473
- Fix inactive region rendering. #8478
- Fix CUDA support not working. #8481
- Fixes for other IntelliSense issues.
- Fix some translations.
Known Issues
- clang-tidy header warnings sometimes don't disappear after the issue is fixed. #8502
- clang-tidy processing status indicator can get stuck after editing/saving a header that is currently being analyzed by clang-tidy. #8504
- onWillSaveTextDocument sometimes times out eventually causing save to fail when clang-tidy is running. (#8474)