[opensuse] language server crashes about vscode-cpptools

[sean-mcmanus]

@linev With 1.20.5, do you see a C/C++ Crash Call Stacks pane in the Output window after waiting 5 seconds after the crash?

[sean-mcmanus]

@linev Does the issue repro with 1.18.5 from November? Do you know which version it started reproing with?

[sean-mcmanus]

@linev From your logging, it appears that it might be crashing while tag parsing tag parsing file: /home/linev/git/webgui/bindings/pyroot/cppyy/CPyCppyy/include/CPyCppyy/PyResult.h. Can you try adding "/home/linev/git/webgui/bindings/pyroot/cppyy/CPyCppyy/include/CPyCppyy": true to your C_Cpp.files.exclude setting to get it to skip tag parsing that file and see if it stops crashing? (also, make sure that logging stops appearing).

[linev]

Can you try adding "/home/linev/git/webgui/bindings/pyroot/cppyy/CPyCppyy/include/CPyCppyy": true to your C_Cpp.files.exclude setting to get it to skip tag parsing that file and see if it stops crashing? (also, make sure that logging stops appearing).

Adding such entry does not help. ....CPyCppyy/PyResult.h still appears in list of parsed files and cpptools crashed.

Does the issue repro with 1.18.5 from November?

This version works! Also versions up to 1.19.1 are working.
But trying to switch to 1.19.2 leads to crash.

[github-actions]

Hey @sean-mcmanus, this issue might need further attention.

@linev, you can help us out by closing this issue if the problem no longer exists, or adding more information.

[linev]

Problem remains, after version 1.19.1 it crashes for me.
The only solution for me - downgrade plugin to 1.18.5

[github-actions]

Hey @sean-mcmanus, this issue might need further attention.

@linev, you can help us out by closing this issue if the problem no longer exists, or adding more information.

[linev]

Problem still exist - also with latest 1.21.0 version

[github-actions]

Hey @sean-mcmanus, this issue might need further attention.

@linev, you can help us out by closing this issue if the problem no longer exists, or adding more information.

[linev]

Problem resolved after Tumbleweed upgrade and switching to v1.22.2 of C/C++ for Visual Studio Code