Sean McManus

Yeah, this bug repros for me. Launching from a command prompt is a workaround, but I always launch VS Code from the Windows task bar. 

Yeah, it could be the JSON.parse call (I didn't see that before, and "readFile" was mentioned so I just assumed that was the cause) -- changing it to use something...

Are you able to locate the source where uint8_t and uint32_t are defined? It's possible there's some incorrect define or intelliSenseMode being used that causes the definition to be skipped...

I hit the problem with 0.29.0-insiders: https://github.com/microsoft/vscode-cpptools/issues/5731 . Thanks for reporting that. I also hit the issue with uint8_t on 0.28.3 -- changing the intelliSenseMode to clang-arm fixed the issue...

Actually, using clang-arm doesn't fix it (it could fix other issues though), but adding "__STATIC_INLINE" to the defines list appears to have fixed it. Not sure if the PlatformIO extension...

Hmm, the clang-arm setting causing missing headers is not expected. Maybe it should be clang-arm64? If the target is 32-bit, it'd be interesting to see if clang-x86 works better or...

FYI, https://github.com/microsoft/vscode-cpptools/releases/tag/0.29.0-insiders2 has the fix for the bug you hit with 0.29.0-insiders, as well as some other fixes we found while working with PlatformIO-based projects.

The C/C++ extension added clang-x86 mode for 32-bit targets in August 2019 -- not sure if PlatformIO has added support for that yet. I also hit a problem using clang-arm...

https://github.com/microsoft/vscode-cpptools/releases/tag/0.30.0-insiders added a bunch of updates to auto-handling of ARM intelliSenseModes and added remote ARM support, so let us know if the configuration has gotten worse or better for you....

I don't think the issue is "stale"...it was just never addressed. What details were needed?