-
Notifications
You must be signed in to change notification settings - Fork 29.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Repetitive problem message when pointing to problem line #5792
Comments
@alexxx537 what language is this? |
It is C language. I am using C/C++ extension. |
This issue was moved to microsoft/vscode-cpptools#41 |
This is not related to the C++ extension as it does not support build not does it process the output. I think this has to do with VSCode processing warnings and errors from Tasks. |
@Aukstkalnis how do you build the project ? |
See this issue: |
@Aukstkalnis Just to double check. The tasks.json must normally sit in a settings folder. This is the case in your setup. |
Sorry a .vscode folder. |
Yes, my task.json is in the .vscode folder which is generated in my project root directory. |
I can't reproduce this using our setup. Here is what I see using version 17.x of cl:
Setting up the problem matcher for this pattern makes the errors show up correctly. @Aukstkalnis how does the output of the nmake run look on your system. |
This is my project example from microsoft/vscode-cpptools#41: With this example I am able to reproduce this problem. |
@Aukstkalnis could you still provide me with the output of running build.bat. You seem to call a g++ compiler and the error format mostly depends on compiler and its version. |
I get this output: c:\Users\aukstkalnis.de\Desktop\ConsoleApplication1>g++ -c hello.cpp |
@Aukstkalnis thanks. Now I see. Need to think about how to best address this. |
@Aukstkalnis this got addressed a while ago by de-duping error message in the problem collector. |
Steps to Reproduce:
It is strange to see list of problem messages that are the same.
The text was updated successfully, but these errors were encountered: