You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: Extension/CHANGELOG.md
+10
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,14 @@
1
1
# C/C++ for Visual Studio Code Changelog
2
2
3
+
## Version 1.20.3: April 30, 2024
4
+
### Enhancement
5
+
* Log `cpptools` and `cpptool-srv` crash call stacks in the 'C/C++ Crash Call Stacks' Output channel for bug reporting (on x64 Linux and x64/arm64 Mac).
6
+
7
+
### Bug Fixes
8
+
* Fix directories being incorrectly recursively traversed in certain cases. [#11993](https://github.com/microsoft/vscode-cpptools/issues/11993)
9
+
* Fix a crash during startup. [#12237](https://github.com/microsoft/vscode-cpptools/issues/12237)
10
+
* Fix IntelliSense configuration on Windows ARM64. [#12253](https://github.com/microsoft/vscode-cpptools/issues/12253)
11
+
3
12
## Version 1.20.2: April 22, 2024
4
13
### Bug Fixes
5
14
* Fix non-existent relative path variables not showing a warning in `c_cpp_properties.json` (and other related issues). [#12089](https://github.com/microsoft/vscode-cpptools/issues/12089)
@@ -25,6 +34,7 @@
25
34
### Bug Fixes
26
35
* Fix an IntelliSense parsing issue. [#6183](https://github.com/microsoft/vscode-cpptools/issues/6183)
27
36
* Fix 'Copy Declaration / Definition' code not being formatted. [#10956](https://github.com/microsoft/vscode-cpptools/issues/10956)
37
+
* Fix semantic colorization of certain macro arguments. [#11416](https://github.com/microsoft/vscode-cpptools/issues/11416)
28
38
* Fix 'Create Declaration / Definition' not working if the cursor isn't on the function name. [#11834](https://github.com/microsoft/vscode-cpptools/issues/11834)
crashCallStacksChannel.appendLine(localize({key: "c.cpp.crash.call.stacks.description",comment: ["{0} is a URL."]},
106
+
"A C/C++ extension process has crashed. The crashing process name, date/time, signal, and call stack are below -- it would be helpful to include that in a bug report at {0}.",
0 commit comments