Repository navigation
0.28.0-insiders3: Tag parsing no longer working #5463
Description
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
Activity
sean-mcmanus commentedon May 12, 2020
0.28.0-insiders3 fixed a bug with compile_commands.json that caused the browse.path (files that get tag parsed) to be missing files (although there are still some cases where file are missed). However, your log show that it's in the middle of tag parsing. Do you still get Find All Refs missing results when the workspace parsing is 100% finished? When you open a file that is failing to get tag parsed, does the Outline still populate with symbols? If so, it would be a regression with our parser.
sean-mcmanus commentedon May 13, 2020
You can add the folders to files.exclude to exclude them from tag parsing.
By "tag parser crashes" you mean fails to parse the files and not cpptools actually crashes, right?
michelleangela commentedon Dec 9, 2020
Closing this issue because it has not had recent activity.