VS Code doesn't offer gcc as a launch configuration

[matej-almasi]

6.1.31-2-MANJARO GNU/Linux
VS Code 1.79.0
C++ extension v1.15.4

Hello everyone. Switched to Manjaro Linux recently and tried to set up some basic c++ environment. I ran into a problem when I press the "play" button and get a prompt to pick a configuration, only "(gdb) launch" is offered to me:

I would expect a list of configurations, at least the ones related to gcc, I double checked if I have it installed.

Furthermore, when I select the offered "(gdb) launch)", no tasks.json is created, only "empty" launch.json and a following error message (of course - launch is empty):

Does anyone know how to fix this? Could this be a distro issue?

By the way, I got the same behavior from both AUR and Snap installed VSC.

[sean-mcmanus]

@matej-almasi That means our extension isn't auto detecting a compiler at the expected locations. Do you know what the path is to the compiler you wanted to use? Is the compiler shown in the dropdown list when running the C/C++: Select IntelliSense Configuration... command?

[sean-mcmanus]

This could also be because you don't have a debugger installed (gdb or lldb). If you check your C/C++ logging you should see a message starting with "Unable to find the" if you're hitting that case (and you would also see the compiler in the C/C++: Select IntelliSense Configuration list since that doesn't exclude compilers without a debugger).

[matej-almasi]

Hello @sean-mcmanus , thanks for the reply.
It appears that both of the VS Code packages I installed were in a "sandbox" mode, preventing the application from properly interacting with the file system. As a Linux beginner, I didn't realize that. I checked the extension on a different distribution, making sure VSC isn't sandboxed. The extension works properly there.

Sorry for not providing this update earlier, I thougt there wouldn't be any replies after waiting a few days for some.