Intellisense squiggles appear even though headers are discovered

[Georacer]

Type: LanguageService

Hello everyone,
I'm having some issues with the Intellisense feature of the C++ extension of VSCode.

Describe the bug

• OS and Version: Ubuntu 18.04
• VS Code Version: 1.34.0
• C/C++ Extension Version: 0.23.1
• Other extensions you installed (and if the issue persists after disabling them): Anaconda Extension Pack, Docker, Gitlens, Python and others
• A clear and concise description of what the bug is:
  I have a ROS workspace, whose source folder I have opened in VSC, with path: "/home/george/ros_workspaces/uav_ftc/src/.
  All local files are visible and all included files which are situated in this folder.

Also, I have included the source files from another program (called ACADO for reference), whose path I have added in the includePath variable of c_cpp extension.

All header files and types of the ACADO source are apparently discovered, since hitting F12 will open and point to the corresponding line.

However, squiggles are broken and exist everywhere the ACADO source is referred. Errors include include errors and undefined identifiers.

I do not wish to turn to Tag Parser engine for intellisense, because apparently it also doesn't squiggle obvious errors, such as actually undefined symbols.

To Reproduce
I'm not sure if I should go all the way and provide you with files for two large projects...

Expected behavior
I expected headers and symbols of the external source files to be parsed and recognized by Intellisense correctly

Screenshots
Example: DifferentialState type looks undefined

but hitting F12 on it leads to its definition:

Additional context
The local c_cpp_properties.json file:

{
    "configurations": [
        {
            "browse": {
                "databaseFilename": "",
                "limitSymbolsToIncludedHeaders": true
            },
            "includePath": [
                "/home/xxx/UserPrograms/ACADOtoolkit/acado/**",
                "/home/xxx/ros_workspaces/uav_ftc/devel/include",
                "/opt/ros/melodic/include",
                "/home/xxx/ros_workspaces/uav_ftc/src/last_letter/last_letter/include",
                "/home/xxx/ros_workspaces/uav_ftc/src/last_letter/mathutils/include",
                "/home/xxx/ros_workspaces/uav_ftc/src/uav_ftc/include",
                "/home/xxx/ros_workspaces/uav_ftc/src/last_letter/uav_utils/include",
                "/usr/include"
            ],
            "name": "Linux",
            "intelliSenseMode": "gcc-x64",
            "compilerPath": "/usr/bin/gcc",
            "cStandard": "c11",
            "cppStandard": "c++17"
        }
    ],
    "version": 5
}

Thank you in advance for your time.
Let me know if additional information is needed or if I have posted in the wrong issue tracker.

[sean-mcmanus]

F12 on #include does not follow the same paths as IntelliSense error squiggles (we haven't gotten around to fixing that bug yet).

So if you're getting squiggles on the headers it means IntelliSense isn't able to find the files via the includePath used.

Can you run the C/C++: Log Diagnostics command with the file with error squiggles to see what IntelliSense settings are getting used and if the includePath can be fixed?

[Georacer]

Sure! Here it is. Blurred out my username, though.

-------- Diagnostics - 6/6/2019, 12:17:16 PM
Version: 0.23.1
Translation Unit Mappings:
[/home/<username>/ros_workspaces/uav_ftc/src/uav_ftc/mpc_models/rate_controller_solver.cpp]:
    /home/<username>/ros_workspaces/uav_ftc/src/uav_ftc/mpc_models/rate_controller_solver.cpp
Translation Unit Configurations:
[/home/<username>/ros_workspaces/uav_ftc/src/uav_ftc/mpc_models/rate_controller_solver.cpp]:
    Process ID: 15450
    Memory Usage: 11 MB
    Compiler Path: /usr/bin/gcc
    Includes:
        /home/<username>/ros_workspaces/uav_ftc/devel/include
        /opt/ros/melodic/include
        /home/<username>/ros_workspaces/uav_ftc/src/last_letter/last_letter/include
        /home/<username>/ros_workspaces/uav_ftc/src/last_letter/mathutils/include
        /home/<username>/ros_workspaces/uav_ftc/src/uav_ftc/include
        /home/<username>/ros_workspaces/uav_ftc/src/last_letter/uav_utils/include
        /usr/include/c++/7
        /usr/include/x86_64-linux-gnu/c++/7
        /usr/include/c++/7/backward
        /usr/lib/gcc/x86_64-linux-gnu/7/include
        /usr/local/include
        /usr/lib/gcc/x86_64-linux-gnu/7/include-fixed
        /usr/include/x86_64-linux-gnu
        /usr/include
        /home/<username>/UserPrograms/ACADOtoolkit/acado
    Standard Version: c++17
    IntelliSense Mode: gcc-x64
    Other Flags:
        --g++
        --gnu_version=70400
Total Memory Usage: 11 MB

[Georacer]

Maybe this is what is wrong:
Even though in the intellisense configuration window, for the Include Path, I have spectified:

/home/<username>/UserPrograms/ACADOtoolkit/acado/**
/home/<username>/ros_workspaces/uav_ftc/devel/include
/opt/ros/melodic/include
/home/<username>/ros_workspaces/uav_ftc/src/last_letter/last_letter/include
/home/<username>/ros_workspaces/uav_ftc/src/last_letter/mathutils/include
/home/<username>/ros_workspaces/uav_ftc/src/uav_ftc/include
/home/<username>/ros_workspaces/uav_ftc/src/last_letter/uav_utils/include
/usr/include

the acado folder isn't actually parsed recursively; note how the /** is omitted in the diagnostic log.
This makes me think that the actual headers (which reside deeper in the folder) are never actually loaded.

[feijie825]

F12 on #include does not follow the same paths as IntelliSense error squiggles (we haven't gotten around to fixing that bug yet).

So if you're getting squiggles on the headers it means IntelliSense isn't able to find the files via the includePath used.

Can you run the C/C++: Log Diagnostics command with the file with error squiggles to see what IntelliSense settings are getting used and if the includePath can be fixed?

How can I make it appear again when I disable these squiggles?

[sean-mcmanus]

@feijie825 You can change the C_Cpp.errorSquiggles setting.

[feijie825]

@sean-mcmanus Thank you. I've tried to change the settings. But it didn't work.

[sean-mcmanus]

@feijie825 How did you disable the squiggles originally?

[Victsz]

Is it possible to take CMakelists, if there is one, as reference for include path searching?

[sean-mcmanus]

@Victsz You can use the CMake Tools extension and set the configurationProvider (in c_cpp_properties.json, or the C_Cpp.default one) to "vector-of-bool.cmake-tools".

[Victsz]

@Victsz You can use the CMake Tools extension and set the configurationProvider (in c_cpp_properties.json, or the C_Cpp.default one) to "vector-of-bool.cmake-tools".

@sean-mcmanus after cmake tools update,

1.2.1
Thank you to the following CMake Tools contributors: koemai, bjosa, emanspeaks, som1lse, dcourtois, tsing80, andy-held, notskm, thezogoth, yokuyuki, dbird137, fabianogk, randshot.

vector-of-bool has moved on to other things and Microsoft is now maintaining this extension. Thank you vector-of-bool for all of your hard work getting this extension to where it is today!

Breaking changes:

The publisher id changes to ms-vscode.cmake-tools.

I change accordingly
"C_Cpp.default.configurationProvider": "ms-vscode.cmake-tools",

but the intellisense engine not working

I tried cmake reconfigure , windows reload, reset intellisense database

[bobbrow]

@Victsz We didn't change the configurationProvider to ms-vscode.cmake-tools yet because we need to make a change to cpptools to support it first. We plan to support both ids during this transition. If you change it back to vector-of-bool.cmake-tools it should work again.