Starting with 0.28.0-insiders3, I noticed that the tag parsing was no longer working. For example, now "Find all references" only works in the current TU (because I assume it relies on the tag parser to find other "potential references" in other TUs?).
I setup cpptools by providing the path to the compile_commands.json in the workspace level settings (I typically open multiple folders but I only configure at the workspace level):
"C_Cpp.default.compileCommands": "/path/to/compile_commands.json",
See attached log files.
"old.log" is 0.27.1 and "new.log" is 0.28.0-insiders3
Notice that in "new.log" the tag parsing does not appear to be working. It seems like it tag parses the headers in the current TU (very slowly?) but nothing else. Every header it tries to parse gets the following error as well:
Tag parsing encountered an error, but it may not matter. Let us know if symbols in the file can't be found
old.log
new.log
Starting with 0.28.0-insiders3, I noticed that the tag parsing was no longer working. For example, now "Find all references" only works in the current TU (because I assume it relies on the tag parser to find other "potential references" in other TUs?).
I setup cpptools by providing the path to the compile_commands.json in the workspace level settings (I typically open multiple folders but I only configure at the workspace level):
"C_Cpp.default.compileCommands": "/path/to/compile_commands.json",
See attached log files.
"old.log" is 0.27.1 and "new.log" is 0.28.0-insiders3
Notice that in "new.log" the tag parsing does not appear to be working. It seems like it tag parses the headers in the current TU (very slowly?) but nothing else. Every header it tries to parse gets the following error as well:
Tag parsing encountered an error, but it may not matter. Let us know if symbols in the file can't be found
old.log
new.log