Intellisense not working?

[sparkwenc]

I am trying to configure c++23 intellisense on MacOS using g++-14 (rather than clang).

The hover works well, but the auto-completion, go-to-definition, etc., simply does not work.

By pressing Shift-Spc, its pops up with "No suggestions."

Is this something wrong with my configuration with intellisense or unsupported behavior for c++23?

[sean-mcmanus]

C++23 with g++-14 is supported on Mac. Can you set C_Cpp.loggingLevel to "Debug" and see if there are any errors reported? Does it work with C++20 or with clang with C++23? Do you have any sample code?

[sparkwenc]

Yes, the Log Diagnostics shows all the expected configurations I used.

I find it weird as well, completion and hover both work fine now, including when I use ::. Only go-to-definition does not work currently.

Perhaps, is there any explicit command to reset this feature?

[sean-mcmanus]

@sparkwenc Go to definition could fail if there's a problem with the database, particularly if the definition is in a different TU (source file). You can try running C/C++: Reset IntelliSense Database to fix it (and wait for the file with the definition to be tag parsed).

You may also want to check the Outline pane to see if the definitions appear there or running the Go to Symbol in Workspace command -- if those don't find the definition, then the symbol is missing from the database for some reason (unrelated to IntelliSense parsing).

[sparkwenc]

Indeed! I run C/C++: Reset IntelliSense Database, and it doesn't fix it. I also checked the Outline pane and tried Go to Symbol in Workspace. They do not have any code symbols contained in my cpp code.

This seems to be a bit similar to the issue reported here 11001, but I haven't found a solution for it.

[sean-mcmanus]

@sparkwenc Do all symbols not appear at all in any workspace? There may be some failure to create the database, so you might try changing C_Cpp.default.browse.databaseFilename to something like "${workspacefolder}/.vscode/vc.db" to ensure the database is able to be created. Otherwise, if you have C_Cpp.loggingLevel set to "Debug" then you might want to check for tag parsing error messages after saving/editing the file with no symbols.

[sparkwenc]

Thank you!!!
I changed C_Cpp.default.browse.databaseFilename from empty to ${default} then the problem is fixed.

[sean-mcmanus]

@sparkwenc Oh, that is unexpected. I don't think ${default} is a valid setting value, so I'm not sure what path is being used. But it sounds like there might have been a permissions issue with the original default path or database file.

[sparkwenc]

I don't know the value of ${default} either, the description of C_Cpp.default.browse.databaseFilename is
"The value to use in a configuration if browse.databaseFilename is either not specified or set to ${default}."

In practice it is writing what is needed into ${workspacefolder}/.vscode/settings.json -- is this expected?

[bobbrow]

Maybe we need to clarify the setting documentation. It's trying to say that the value of C_Cpp.default.browse.databaseFilename is used if you set the value of browse.databaseFilename to ${default} in your c_cpp_properties.json file. Like this:

c_cpp_properties.json

{
    "configurations": [
        {
            "name": "foo",
            "browse": {
               "databaseFilename": "${default}"
            }
        }
    ]
}