Peek References does not work on struct's members

[mehlian]

Environment

• OS and Version: Windows 10
• VS Code Version: 1.108.2
• C/C++ Extension Version: C/C++ v1.32.2
• If using SSH remote, specify OS of remote machine: none

Bug Summary and Steps to Reproduce

Bug Summary:
No result found when using 'Peek References' on struct members.

Steps to reproduce:

1. Paste code (file.hpp):

struct MyStruct
{
    int value;
};

struct Container
{
    int value2;
    MyStruct *myStruct;
};

void func(Container *container)
{
    container->myStruct = 0;
}

void func2(Container *container)
{
    container->value2 = 1;
    container->myStruct = 0;
}

2. Use 'Peek References' option (Shift+F12) when over 'myStruct' or 'value2' variable (inside function or at struct definition).
3. See 'No references found for 'myStruct'.

Expected behavior:
Peek windows should appear and show all places where 'myStruct' member is used.

Configuration and Logs

ask for specific details

Other Extensions

No response

Additional context

No response

[sean-mcmanus]

@mehlian I don't repro the issue. This symptom might occur if your database isn't completely populated yet -- check the C/C++ logging for [Warning] Some references may be missing, because workspace parsing was incomplete when Find All References was started.. It's also possible something is preventing your database from being created (in which case you may not see symbols in the Outline view either). Also, there could be some IntelliSense errors or crashes if there were some additional code being included in the TU, in which case you might also notice those in the logging.

[mehlian]

I've created new folder with single file containing example code and it works as expected there. But somehow it doesn't work in my project folder where I created this dummy example. I don't see any warnings in C/C++ logs.

Any tips where to look for? Is there any way to refresh 'database'?

Thanks for quick responses.

[sean-mcmanus]

@mehlian You can run the C/C++: Reset IntelliSense Database command to reset the database. Also, if you set the setting "C_Cpp.default.browse.databaseFilename": "${workspaceFolder}/.vscode/vc.db" or something equivalent (i.e. easily findable, but if it's the open file scenario then ${workspaceFolder} should be replaced by some other path) then it makes it easier to verify the database. Usually, if there's a major error the database won't exist or it'll be really small. You can also examine the database with a sqlite editor and Copilot is usually able to use python to generate sql commands to query it, but you probably shouldn't examine a live instance of the database while our extension is modifying it.

Are you saying you repro the issue in the "open file" scenario? I tried that but still didn't repro it.

UPDATE: Okay, it sounds like you repro it with a particular project. There might be some configuration issue with that project. I would check the logging for errors and/or try to somehow isolate what is special about that project that could trigger the repro, and/or link to if it's open source.

[mehlian]

'C/C++: Reset IntelliSense Database' command fixed the issue.

Yes it looks like the issue was with this particular project.
This project was using old vscode version (~2 years old) and old vscode-cpptools extension (~2 years old).
I've recently updated vscode to version 1.108.2 and this triggered vscode-cpptools update to latest version.

My guess is that my old 'database' was not compatible with new implementation and this started issues where for every newly created files 'Peek References' and 'Rename Symbol' didn't work but it worked on old files (and old symbols imported to new files).

You can close this bug report if you think my answer explains the problem.

[sean-mcmanus]

@mehlian Our code checks the database version and is supposed to reset the database when it detects an incompatible older version, but it is possible that some database corruption might have occurred (or the database might have might have still been regenerating after you updated to the latest version). If there is an actual bug, I don't think we have enough information, but we are actively working on making the database and sqlite operations more reliable in other issues we're tracking internally.