Type: LanguageService

**----- Input information below -----**

**Type: LanguageService**

**Describe the bug**

- OS and Version:

- A clear and concise description of what the bug is.

**To Reproduce**

Steps to reproduce the behavior:

*Providea code sample including configuration files such as c_cpp_properties.json*

1. Go to '...'

2. Click on '....'

3. Scroll down to '....'

4. See error

**Expected behavior**

A clear and concise description of what you expected to happen.

**Screenshots**

If applicable, add screenshots to help explain your problem.

**Additional context**

If you are experiencing a problem that we are unable to diagnose based on information in your issue report, we might ask you to enable logging and send us your logs.

As of version 0.14.0 of the extension, logging information is now delivered directly to the Output window in VSCode. To turn on full logging for an issue report, add`"C_Cpp.loggingLevel": "Information"` to your**settings.json**.

As of version 0.14.0 of the extension, logging information is now delivered directly to the Output window in VSCode. To turn on full logging for an issue report, add`"C_Cpp.loggingLevel": "Information"`or`"C_Cpp.loggingLevel": "Debug"`to your**settings.json**.



VS Code organizes the logging from different extensions to improve readability so you must select the "C/C++" option in the log filter selector to see logging from the C/C++ extension:

When you set the`compilerPath` property and change`intelliSenseMode` to`clang-x64`, you no longer need to copy the system include path or defines to`includePath`,`browse.path`, or`defines` to enable IntelliSense to work properly. For example:

When you set the`compilerPath` property and change`intelliSenseMode` to`clang-x64` (or`gcc-x64` in version 0.18.0 and higher), you no longer need to copy the system include path or defines to`includePath`,`browse.path`, or`defines` to enable IntelliSense to work properly. For example:

{

"name":"MinGW",

"intelliSenseMode":"clang-x64",

"intelliSenseMode":"gcc-x64",

"compilerPath":"C:/mingw64/bin/gcc.exe",

"includePath": [

],

"defines": [],

"browse": {

"path": [

],

"limitSymbolsToIncludedHeaders":true,

"databaseFilename":""

},

"cStandard":"c11",

"cppStandard":"c++17"

}

To use the Windows Subsystem for Linux with this extension you need to add a configuration to your**c_cpp_properties.json** file which adds the necessary header paths from within the WSL filesystem to the`includePath`.

{

"name":"WSL",

"intelliSenseMode":"clang-x64",

"intelliSenseMode":"gcc-x64",

"compilerPath":"/usr/bin/gcc",

"includePath": [

"${workspaceFolder}",

"/mnt/c/libraries/lib1/include",

],

"defines": [],

"browse": {

"path": [

"${workspaceFolder}",

],

"limitSymbolsToIncludedHeaders":true,

"databaseFilename":""

},

"cStandard":"c11",

"cppStandard":"c++17"

}

A friendly name for the configuration. "Linux", "Mac", and "Win32" are special names that instruct the extension to load that configuration by default on the associated operating system unless additional configurations have been created. The status bar in VS Code will show you which configuration is active. You can also click on the label in the status bar to change the active configuration.

If`"C_Cpp.intelliSenseEngine"` is set to "Default" in your settings file, this property determines which mode the IntelliSense engine will run in.`"msvc-x64"` maps to Visual Studio mode with 64-bit pointer sizes.`"clang-x64"` maps toGCC/CLang mode with 64-bit pointer sizes. Windows uses`"msvc-x64"` by defaultand Linux/Mac use`"clang-x64"` by default.

If`"C_Cpp.intelliSenseEngine"` is set to "Default" in your settings file, this property determines which mode the IntelliSense engine will run in.`"msvc-x64"` maps to Visual Studio mode with 64-bit pointer sizes.`"clang-x64"` maps to CLang mode with 64-bit pointer sizes.`"gcc-x64"` maps to GCC mode with 64-bit pointer sizes.Windows uses`"msvc-x64"` by default, macOS uses`"clang-x64"` by default,and Linux uses`"gcc-x64"` by default.

If`"C_Cpp.intelliSenseEngine"` is set to "Default" in your settings file, this list of paths will be used by IntelliSense to search for headers included by your source files. This is basically the same as the list of paths you pass to your compiler with the`-I` switch. If a path ends with`/**` the IntelliSense engine will do a recursive search for includes starting from that directory. If on Windows with Visual Studio installed, or if a compiler is specified in the`compilerPath` setting, it is not necessary to list the system include paths in this list.

This list of paths will be used by the Tag Parser to search for headers included by your source files. The Tag Parser will automatically search all subfolders in these paths unless the path ends with a`/*` or`\*`. For example,`/usr/include` directs the Tag Parser to search the`include` folder and its subfolders for headers while`/usr/include/*` directs the Tag Parser not to look in any subfolders of`/usr/include`.

This list of paths will be used by the Tag Parser to search for headers included by your source files.If omitted,`includePath` will be used as the`path`.The Tag Parser will automatically search all subfolders in these paths unless the path ends with a`/*` or`\*`. For example,`/usr/include` directs the Tag Parser to search the`include` folder and its subfolders for headers while`/usr/include/*` directs the Tag Parser not to look in any subfolders of`/usr/include`.

When true, the Tag Parser will only parse code files that have been directly or indirectly included by a source file in`${workspaceFolder}`. When false, the Tag Parser will parse all code files found in the paths specified in the**path** list.

.vscode-test/

.vscode-test/

* Change the symbol database to update without needing to save.[#202](https://github.com/Microsoft/vscode-cpptools/issues/202)

* Enable IntelliSense-based`Go to Definition` for the current translation unit, including local variables and overloaded operators.[#255](https://github.com/Microsoft/vscode-cpptools/issues/255),[#979](https://github.com/Microsoft/vscode-cpptools/issues/979)

* Improved the`Go to Definition` performance with large workspaces and files with lots of`#include`s.[#273](https://github.com/Microsoft/vscode-cpptools/issues/273)

* Disable`Go to Definition` for invalid tokens, e.g. comments, strings, keywords, etc.[#559](https://github.com/Microsoft/vscode-cpptools/issues/559)

* Add`C_Cpp.updateChannel` setting for easier access to Insider builds of the extension.[#1526](https://github.com/Microsoft/vscode-cpptools/issues/1526)

* Add support for v2 of the configuration provider API.[#2237](https://github.com/Microsoft/vscode-cpptools/issues/2237)

* Fix bug with parsing definitions in`compile_commands.json`.[#2305](https://github.com/Microsoft/vscode-cpptools/issues/2305)

* Fix`sh` failure when attaching to a remote Linux process.[#2444](https://github.com/Microsoft/vscode-cpptools/issues/2444)

* Fix incorrect default`cl.exe` macro.[PR#2468](https://github.com/Microsoft/vscode-cpptools/issues/2468)

* Fix multiple bugs with the symbols in the Outline view not updating correctly.[#2477](https://github.com/Microsoft/vscode-cpptools/issues/2477),[#2500](https://github.com/Microsoft/vscode-cpptools/issues/2500),[#2504](https://github.com/Microsoft/vscode-cpptools/issues/2504)

* Add support for`workspaceFolderBasename` expansion.[#2491](https://github.com/Microsoft/vscode-cpptools/issues/2491)

* Gabriel Arjones (@g-arjones)[PR#2495](https://github.com/Microsoft/vscode-cpptools/pull/2495),[PR#2503](https://github.com/Microsoft/vscode-cpptools/pull/2503)

* Fix bug with variable resolution.[#2532](https://github.com/Microsoft/vscode-cpptools/issues/2532)

* Fix off-by-one bug with hover and`Go to Definition`.[#2535](https://github.com/Microsoft/vscode-cpptools/issues/2535)

* Fix 0.18.0 regression causing non-MinGW compilers to use`-fms-extensions` on Windows.[#2424](https://github.com/Microsoft/vscode-cpptools/issues/2424),[#2425](https://github.com/Microsoft/vscode-cpptools/issues/2425)

* Add the`C_Cpp.intelliSenseEngine` setting value of`Disabled` (for users who only use the debugger).[#785](https://github.com/Microsoft/vscode-cpptools/issues/785)

* Add`C_Cpp.workspaceSymbols` setting with default`Just My Code` to filter out system header symbols.[#1119](https://github.com/Microsoft/vscode-cpptools/issues/1119),[#2320](https://github.com/Microsoft/vscode-cpptools/issues/2320)

* Add`C_Cpp.inactiveRegionForegroundColor` and`C_Cpp.inactiveRegionBackgroundColor` settings.[#1620](https://github.com/Microsoft/vscode-cpptools/issues/1620),[#2212](https://github.com/Microsoft/vscode-cpptools/issues/2212)

* John Patterson (@john-patterson)[PR 2308](https://github.com/Microsoft/vscode-cpptools/pull/2308)

* John Patterson (@john-patterson)[PR#2308](https://github.com/Microsoft/vscode-cpptools/pull/2308)

* Add`gcc-x64``intelliSenseMode` and send the correct clang or gcc version to our parser, fixing various IntelliSense errors.[#2112](https://github.com/Microsoft/vscode-cpptools/issues/2112),[#2175](https://github.com/Microsoft/vscode-cpptools/issues/2175),[#2260](https://github.com/Microsoft/vscode-cpptools/issues/2260),[#2299](https://github.com/Microsoft/vscode-cpptools/issues/2299),[#2317](https://github.com/Microsoft/vscode-cpptools/issues/2317)

* Make`Go to Definition` on the definition go to the declaration instead.[#2298](https://github.com/Microsoft/vscode-cpptools/issues/2298)

* Add multi-pass environment variable resolution allowing variables defined in terms of other variables.[#2057](https://github.com/Microsoft/vscode-cpptools/issues/2057)

* John Patterson (@john-patterson)[PR 2322](https://github.com/Microsoft/vscode-cpptools/pull/2322)

* Allow users to use`~` for`${userProfile}` on Windows.[PR 2333](https://github.com/Microsoft/vscode-cpptools/pull/2333)

* John Patterson (@john-patterson)[PR#2322](https://github.com/Microsoft/vscode-cpptools/pull/2322)

* Allow users to use`~` for`${userProfile}` on Windows.[PR#2333](https://github.com/Microsoft/vscode-cpptools/pull/2333)

* Add support for compiler flags`-fms-extensions` and`-fno-ms-extensions` on Windows (the default for MinGW-based compilers).[#2363](https://github.com/Microsoft/vscode-cpptools/issues/2363)

* Make completion "show more results" (i.e. inaccessible members) when invoked a 2nd time.[#2386](https://github.com/Microsoft/vscode-cpptools/issues/2386)

* Fix attach to process for systems without`bash` by using`sh` instead.[#569](https://github.com/Microsoft/vscode-cpptools/issues/569)

* Andy Neff (@andyneff)[PR 2340](https://github.com/Microsoft/vscode-cpptools/pull/2340)

* Andy Neff (@andyneff)[PR#2340](https://github.com/Microsoft/vscode-cpptools/pull/2340)

* Fix IntelliSense crash after hover or completion with`_Complex` types.[#689](https://github.com/Microsoft/vscode-cpptools/issues/689),[#1112](https://github.com/Microsoft/vscode-cpptools/issues/1112)

* Fix`files.exclude` not working to exclude non-workspace folders from symbol parsing.[#1066](https://github.com/Microsoft/vscode-cpptools/issues/1066)

* Fix`Switch Header/Source` to give results that match the parent folder name before using just the file name.[#1085](https://github.com/Microsoft/vscode-cpptools/issues/1085)

<h2class="caption">June 2018 Update</h2>

<div>Thank you for installing the C/C++ extension. In the June update, we focused on workspace configuration improvements.<br/>

<h2class="caption">September 2018 Update</h2>

<div>Thank you for installing the C/C++ extension. In the September update, we added a preview of semantic-aware Go To Definition. This allows Go To Definition to work for local variables.

In addition, when the Go To Definition request references a symbol defined in the current translation unit, other incorrect symbols in the workspace with the same identifier will be

filtered from the results.<br/>

We dramatically improved the performance of recursive includes (e.g. using<code>${workspaceFolder}/**</code> in your<code>includePath</code>), we will prompt you to

use compile_commands.json if it is found in your workspace, and we made the<code>browse.path</code> setting optional in the case that it is identical to your<code>includePath</code>.<br/>

We also added a new setting:<code>C_Cpp.updateChannel</code> to facilitate installing Insiders releases of the C++ extension.<br/>

Additional features and bug fixes are detailed in the<ahref="https://github.com/Microsoft/vscode-cpptools/releases">full release notes</a>.</div>

<h3class="caption">Blog Posts</h3>

<div><ahref="https://blogs.msdn.microsoft.com/vcblog/2018/05/08/visual-studio-code-cc-extension-may-2018-update-intellisense-configuration-just-got-so-much-easier/">May 2018 Update</a></div>

<div><ahref="https://blogs.msdn.microsoft.com/vcblog/2018/03/29/visual-studio-code-cc-extension-march-2018-update/">March 2018 Update</a></div>

<div><ahref="https://blogs.msdn.microsoft.com/vcblog/2018/02/20/visual-studio-code-cc-extension-feb-2018-update/">February 2018 Update</a></div>

<div><ahref="https://blogs.msdn.microsoft.com/vcblog/2018/08/23/visual-studio-code-c-c-extension-august-2018-update/">August 2018 Update</a></div>

<div><ahref="https://blogs.msdn.microsoft.com/vcblog/2018/07/25/visual-studio-code-cc-extension-july-2018-update-and-intellisense-auto-configuration-for-cmake/">July 2018 Update</a></div>

<div><ahref="https://blogs.msdn.microsoft.com/vcblog/2018/06/21/visual-studio-code-cc-extension-june-2018-update/">June 2018 Update</a></div>

<div><ahref="https://blogs.msdn.microsoft.com/vcblog/2016/03/31/cc-extension-for-visual-studio-code/">C/C++ Extension anouncement</a></div>

"-D_MSC_FULL_VER=191426428",

"-D_MSC_BUILD=0",

"-D_M_X64=100",

],

"defaults_op" :"merge"

}

"-D_MSC_FULL_VER=191426428",

"-D_MSC_BUILD=0",

"-D_M_X64=100",

],

"defaults_op" :"merge"

}