Vscode-cpptools: Go to declaration always shows 2 files, relative and absolute paths

[idanemergi]

Type: LanguageService

Describe the bug

• OS and Version: Ubuntu 14.04.5
• VS Code Version: 1.24.1
• C/C++ Extension Version:
• Other extensions you installed (and if the issue persists after disabling them): yes
• A clear and concise description of what the bug is.

The issue is that my workspace folders setting contains only the current dir "." and ctrl+p
open file using the relative path, BUT, the problems tab show the problems in the same file
but with the absolute path and when I click on a problem, it opens the same file twice.
1 with relative and 1 with absolute path.
It also happens with "goto declaration", it shows 2 files, 1 with relative, and with absolute path.
Is there a way to use only relative or absolute path?

Steps to Reproduce:

1. Open file using ctrl+p
2. Click on the of the problems in that file from the problems tab

Expected behavior

If the file already open, it should navigate from the problems tab to the open file

Screenshots

goto reference screen shot:

[idanemergi]

anyone? this is really frustrating...

[sean-mcmanus]

This isn't an issue with our C/C++ extension is it? Can you file a VS Code bug at https://github.com/Microsoft/vscode? Who is outputting the absolute paths?

[bobbrow]

Sometimes this happens during a build task. Are you building your code when these two references appear, or just opening files wth ctl+p? If not, can you share your workspace folder settings? I'm not sure what exactly you mean when you say it contains only the current dir ".".

[idanemergi]

This isn't an issue with our C/C++ extension is it? Can you file a VS Code bug at https://github.com/Microsoft/vscode? Who is outputting the absolute paths?

cpptools is my only extension which shows errors in the problems window with absolute path.
for example, I have 'code spell checker' extension which always shows the relative path.
And as I mentioned, it also happens with cpptools goto reference

thanks for your help.

[idanemergi]

Sometimes this happens during a build task. Are you building your code when these two references appear, or just opening files wth ctl+p? If not, can you share your workspace folder settings? I'm not sure what exactly you mean when you say it contains only the current dir ".".

this is my workspace setting file:
{
"folders": [
{
"path": "."
}
],
}

I've only included the workspace folder, I've also tried replacing the "." with the absolute path.
I build the project in a way that all the source code I need has a symbolic link in the workspace folder.
cause I have a very big project and I didn't want IntelliSense to tag all of it.
So my workspace contains the workspace file and a couple of symbolic links.

thanks for your help.

[sean-mcmanus]

I am not able to observe absolute paths coming from our extension. What errors are appearing the problem window exactly? Our IntelliSense errors and gcc problem matcher use workspace relative paths. I see Go to Declaration using relative paths as well.

Does this problem occur with your particular setup or does it repro for a newly created folder? It sounds like the symlink may be the cause.

[idanemergi]

I am not able to observe absolute paths coming from our extension. What errors are appearing the problem window exactly? Our IntelliSense errors and gcc problem matcher use workspace relative paths. I see Go to Declaration using relative paths as well.

Does this problem occur with your particular setup or does it repro for a newly created folder? It sounds like the symlink may be the cause.

You are right, it seems to be the symbolic link causing that.
I tried w/o them and the issue is gone.
Is there a way to workaround it?

[sean-mcmanus]

I don't know a workaround yet. It sounds like a bug. On Linux with a symlinked folder, I'm seeing errors getting shown for the symlink target, causing squiggles to not appear in the current file, and a different file to get opened when the erorr window is clicked (i.e. the symlink target) -- is that the same bug you're seeing? I don't understand how to repro the absolute path in the Go to Declaration.

[yatian-liu]

I have also encountered similar issues, and I previously filed the issue in the vscode repo, which can be seen at this link. I think this may be helpful.

[dev-guy]

I have also encountered similar issues, and I previously filed the issue in the vscode repo, which can be seen at this link. I think this may be helpful.

That issue has been closed as being a problem with this extension.

[jamietre]

I have also encountered similar issues, and I previously filed the issue in the vscode repo, which can be seen at this link. I think this may be helpful.

That issue has been closed as being a problem with this extension.

Just fyi, I'm experiencing almost this exact same issue, but I _do not have_ this extension installed. I filed an issue for vscode which was closed as a duplicate, though I disagree with that assessment (the issue identified as the dup seems different). No resolution at this time.

[sean-mcmanus]

@dev-guy I don't think this issue is related to yours. I think you want https://github.com/microsoft/vscode-cpptools/issues/2375 and https://github.com/microsoft/vscode-cpptools/issues/4206 . I did look into fixing our symlink issues and wrote up a walkthrough on the changes required, but it was too big of a change, so it got pushed back until we can finish other higher priority tasks we're working on (e.g. new multi-root implementation).

What Microsoft employee do you want us to talk with? We usually communicate with the VS Code team via GitHub or email, because most of them are not working at the same time as our C/C++ team.

[farqq]

Is there any solution now?

[sean-mcmanus]

@farqq Not yet.

[occia]

Is there any plan to fix this?

[sean-mcmanus]

@occia There are no definitive plans currently (i.e. it's not on our next milestone), but we have a number of symlink-related bugs that would be good to fix eventually, so this would be part of that. More upvotes would help.

[Victsz]

Is there any solution now?

[sean-mcmanus]

@Victsz There is no solution yet. If this becomes fixed, we'll most likely mark this issue as "Fixed (pending release)" and close it.

[o-u-p]

mark