VSCode settings

[kclauah]

Hello,

I am trying to debug a sample program using VSCode with nRF Connect SDK v1.7.0.

1. #include errors detected based on information provided by the configurationProvider setting. Squiggles are disabled for this translation unit (C:\zephyr\v1.7.0\nrf\samples\event_manager\src\main.c).

2. cannot open source file "event_manager_priv.h" (dependency of "event_manager.h")

Even vscode show errors, the program can successfully build and debug. How can I fix these squiggles errors?

[Amanda Hsieh]

Hi, 

Our VS code team is looking into the issue, and it requires more time. I will be back if I have anything to update.

Regards,
Amanda  

[kclauah]

Thank you. I’ll wait to hear back from you.

In addition, I encounter more questions.

How to stop the program automatically if something unexpected happened? Such as stack overflow, etc...

Because last week I was debugging nRF9160 related program and stack overflow appeared. After few times of ungraceful disconnection to the internet, the modem enter %MDMEV: RESET LOOP.

I have to wait 30 minutes and cannot do anything to skip this period.

[Amanda Hsieh]

Hi, 

Have you tried CONFIG_RESET_ON_FATAL_ERROR=n?

-Amanda

[Michael Jones]

Hi kclauah, would it be possible for you to share the output of the "C/C++: Log Diagnostics" command if you run that from the command palette after opening up, say, the main.c file from the project? It would be interesting to see if we're providing the correct include paths to the C/C++ intellisense.

I can reproduce the issue you are seeing if there is no build for the project as we rely on the information in the build folder (specifically the compile_commands.json file) to figure out the exact include paths required for the project and we provide those to the C/C++ extension as part of a config value. If I do a build of the project, then it starts to work ok though as the build & include information is there.