vscode always reports spurious cuda errors

[vipcxj]

Environment

• OS and Version: win 7
• VS Code Version: 1.96.2
• C/C++ Extension Version: 1.22.11
• If using SSH remote, specify OS of remote machine: Linux node6 6.8.0-49-generic # 49~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Nov 6 17:42:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

Bug Summary and Steps to Reproduce

And I am sure the vscode has detect this file as cuda c++ file

And this file can be compiled successfully.

And in the command window，I type nvcc --version

nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2023 NVIDIA Corporation
Built on Wed_Nov_22_10:17:15_PST_2023
Cuda compilation tools, release 12.3, V12.3.107
Build cuda_12.3.r12.3/compiler.33567101_0

Configuration and Logs

The nvcc compiler could not be found: nvcc
The nvcc compiler could not be found: nvcc
The host compilation command is not found in the output of nvcc.
The host compilation command is not found in the output of nvcc.
The host compilation command is not found in the output of nvcc.

Other Extensions

No response

Additional context

It seems this issue relate to #4218, vscode unable to resolve the env PATH.

[Colengms]

Hi @vipcxj . Are you seeing those exact error messages? I am not finding those exact error messages in the C/C++ Extension. (Though, perhaps that's because you've translated what you're seeing to English?)

Could you try setting "C_Cpp.loggingLevel": "7"? That should enable some very verbose logging, and should log the command lines and outputs related to NVCC detection, to your C/C++ output channel. Could you provide that output? That should give us some idea what's going wrong.

[vipcxj]

@Colengms I translate what I am seeing to English. I work on a remote project.
After I delete C:\Users\XXX\AppData\Roaming\Code on host and \home\XXX\.vscode-server on remote server. It seems that cpptools can locate the nvcc now. And in the log I found NVCC: nvcc fatal : Unknown option '-fsanitize=address'.
Then I change

add_compile_options($<$<CXX_COMPILER_ID:GNU>:-fsanitize=address>)

to

add_compile_options($<$<COMPILE_LANG_AND_ID:CXX,GNU>:-fsanitize=address>)

Now all errors disappeared.