Outline view got to source not always correct

[sidprice]

Version: 1.56.2 (system setup)
Commit: 054a9295330880ed74ceaedda236253b4f39a335
Date: 2021-05-12T17:13:13.157Z
Electron: 12.0.4
Chrome: 89.0.4389.114
Node.js: 14.16.0
V8: 8.9.255.24-electron.0
OS: Windows_NT x64 10.0.19042

In some files if I double click on a function in the Outline view the editor window goes to the wrong place. How do I clear whatever cache is causing this, in general the go to source from the Outline view works well. Just a couple of files that seem "broken".

[sean-mcmanus]

There could be an error parsing the symbols in the file. If the file relies on a macro that breaks our parser, you may need to add the macro to a cpp.hint file (https://docs.microsoft.com/en-us/cpp/build/reference/hint-files?view=msvc-160).

Editing/saving the file should cause a refresh of the document symbols.

Are you able to provide a code sample of the issue?

[sean-mcmanus]

It's in the bottom right status bar -- I re-watched your video and see it's UTF-8 so that should be okay.

Could you possibly have a different extension installed that could be providing those symbols? You can verify if our extension is being used because you should see no main() symbol with the code below (unless #define foo is added to a cpp.hint file):

#define foo

int main() foo
{
    return 0;
}

[sean-mcmanus]

Cool to hear that Reset fixed it -- we just use a sqlite database...not sure exactly how the database could be in a state where only some of the symbols in the file are invalid...hopefully that is a rare occurance.

[sidprice]

Thank you so much for being a great, responsive help. I love VSCode and this has been bugging me for quite a while now :)

[sean-mcmanus]

Yeah, no problem. I was thinking editing the file was supposed to update the database for all the symbols in the file, but I think the code got optimized to do a diff so only a subset of the document symbols get updated, which would explain why the Reset would be needed to refresh old symbol data. Let us know if you find a repro for getting the database into the bad state...seems like the file changed but the symbol incorrectly didn't get updated.

[sidprice]

Sure, I will try to note the trigger if I can :)