Colen Garoutte-Carson

Is this a bug? This seems by-design. We shouldn't do any "shell escaping" for include paths. Not only aren't they on a command line, but they aren't being interpreted in...

This should be addressed in 1.19.4.

Hi @Zes-MinKey-Young . The log you posted indicated version 1.17.5 of the C/C++ extension. Are you still experiencing this issue with the latest version? We have since addressed a known...

Hi @ruilvo . Thanks for suggesting this.

Hi @Zes-MinKey-Young . Since we're not tracking an issue impacting everyone, there would seem to be something about your environment or configuration that we may need to identify to reproduce...

Hi @shenjiangqiu . Could you open a new issue with your repro details? Since this issue is very general and not yet understood, it's possible you're seeing something with a...

Hi @shenjiangqiu . Could you open a new issue and provide the information requested in the new issue template? There are many possible reasons a crash can occur, and it's...

Hi @tripleslash . Thank you for reporting this. The crash appears to relate to parsing a particular file, possibly `C:\DEV\WASHTEC\WASHTEC-BACKEND\DEPS\CMDLIME\COMMANDLINEREADER.H`. Can you confirm? Would it be possible to isolate the...

Hi @tripleslash . I'm unable to reproduce this issue using the contents of https://github.com/kamchatka-volcano/cmdlime and version 1.18.5 of the C/C++ Extension. With `commandlinereader.h` opened (either alone or in the context...

Hi @SimonLeeGit . Could you open a new issue, and provide the information requested in [our new issue template](https://github.com/microsoft/vscode-cpptools/issues/new?assignees=&labels=&projects=&template=1_language-service.yml)? It's likely the crash you are encountering doesn't have the same...