Colen Garoutte-Carson

Hi @Raphael-Hao . Thanks for reporting this. I can repro the issue and have made a fix, which should be available in our next release. (1.22.0) Some background: To support...

Hi @BluTree . The crash looks to be related to parsing of specific source code. Would you be able to isolate the source code involved to provide a stand-alone repro...

Hi @alephpiece . Thanks for reporting this. I've opened a bug (2285676) internally against the IntelliSense component shared with VS.

Hi @pjyoung-ibm . Thank you for reporting this issue. I can reproduce it.

Hi @spinicist . I'm having some difficulty reproducing the issue, with 1.20.5 on an M1 Mac. Following your repro steps (and updating my c_cpp_properties.json to match the content you provided),...

Hi @spinicist . I haven't forgotten about this, but I'm still not able to repro and am blocked from fully configuring IntelliSense (by using CMake Tools) due to the error...

Hi @spinicist . The most recent stack you provided would appear to be a different issue. It appears to be an IntelliSense crash (from the cpptools-srv process, not cpptool), appears...

Hi @vis4rd . The reason MSVC headers are being indexed is that it's effectively still part of your configuration. The C/C++ Extension will detect a 'default' compiler if `compilerPath` is...

Hi @vis4rd > So my guess is cl.exe should not be present in Current Configuration As I mentioned, `cl.exe` is part of your current configuration. If you'd prefer a compiler...

> I still don't understand why my current configuration chooses cl.exe Perhaps we're having a miscommunication about the term "current configuration". If you're referring to the configuration of IntelliSense for...