Skip to content

Releases: microsoft/vscode-cpptools

1.9.6-prerelease1

18 Mar 03:00
a250a53
Compare
Choose a tag to compare
1.9.6-prerelease1 Pre-release
Pre-release

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

1.9.4-debug (Windows x64)

15 Mar 01:17
a07c8fd
Compare
Choose a tag to compare
Pre-release

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

  • Fix temp files randomly not getting deleted on Windows with a C_Cpp.loggingLevel of Warning or greater. #9008
  • Fix mingw clang being detected as gcc. #9024

1.9.4-prerelease1

15 Mar 06:20
a07c8fd
Compare
Choose a tag to compare
1.9.4-prerelease1 Pre-release
Pre-release

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.

1.8.4

07 Feb 23:47
d4df455
Compare
Choose a tag to compare

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.

1.8.2

01 Feb 00:49
3b4c8e7
Compare
Choose a tag to compare

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 the C_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 the maxMemory 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 } and else. #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.

1.8.1 (insiders4)

28 Jan 02:47
abc3c11
Compare
Choose a tag to compare
1.8.1 (insiders4) Pre-release
Pre-release

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 of 1.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

  • 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

1.8.0-insiders3

19 Jan 00:29
88f0bbe
Compare
Choose a tag to compare
1.8.0-insiders3 Pre-release
Pre-release

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 of 1.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

1.8.0-insiders2

08 Dec 00:37
7f99606
Compare
Choose a tag to compare
1.8.0-insiders2 Pre-release
Pre-release

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)

1.8.0-insiders

30 Nov 04:21
27d1ac3
Compare
Choose a tag to compare
1.8.0-insiders Pre-release
Pre-release

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

New Features

  • 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 the C_Cpp.codeAnalysis.maxConcurrentThreads setting. #2908.

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 the maxMemory settings (memory usage from code analysis is not handled yet). #4811
  • 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 newlines not being handled in comments with a Doxygen tag. #5741
  • Fix files.exclude not working for directories external to the active workspace folder. #6877
  • Fix a bug with vcFormat inserting additional spaces between } and else. #7731
  • 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 MS extensions not being enabled by default for Cygwin. #8353
  • 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 an issue in which multiple (potentially different) diagnostics were delivered for headers shared by multiple TUs.

Other

Known Issues

  • Inactive regions don't appear as inactive. #8478
  • CUDA support stopped working. #8481
  • If code analysis is running, saving of header files can fail if clang-tidy is using the header file from a TU that is different from the "default" one chosen by IntelliSense. The workaround is to click the flame icon and choose "Cancel clang-tidy" (or if that fails, kill the clang-tidy processes). #8473
  • C_Cpp.codeAnalysis.maxConcurrentThreads incorrectly has a max of half of C_Cpp.maxConcurrentThreads (instead of just using that as the default). #8471
  • There are some other "known" issues with the "code analysis" feature that are being tracked internally.

1.7.1

20 Oct 02:52
a18b91b
Compare
Choose a tag to compare

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 an extension crash that occurred on activation while a workspace is open with no folders in it. #8280
  • Fix an issue in which configuration defaults were not properly applied. #8298

Known Issues

  • None so far.