May 18, 2022 at 14:10 #32639
I have a visual gdb project in Visual Studio 2022 that is running and compiling ok but the intellisense does not seem to be picking up and highlighting keywords from included file.
ie: built-in keywords like variable types, return, void etc are highlighted but not library function names like ESP_LOGI, xSemaphore, TimerHandle_t etc. Also not seeing the autocomplete suggestions when I start typing the function.
The VisualGDB settings are set to “Advanced Clang Intellisense” , which is only one supported by look of it.
The project is using GCC8.2 and esp-idf 4.4.1
UPDATE: When I close and restart Visual studio, the intellisense starts working again.
Anyone have an idea what would cause it to stop during code writing and come back on reboot?
May 20, 2022 at 08:39 #32660
- This topic was modified 1 month, 1 week ago by orbitcoms.
Unfortunately, it is hard to suggest anything specific based on the description you provided.
In order for us to provide any help with this, we need to be able to reproduce the problem on our side.
Please provide complete and detailed steps to reproduce the issue as described below:
- The steps should begin with launching Visual Studio. They should include every step necessary to create the project from scratch and reproduce the issue.
- Please make sure the steps do not involve any 3rd-party code as we will not be able to review it. If the problem only happens with a specific project, please make sure you can reproduce it on a clean project created from scratch.
- The steps should include uncropped screenshots of all wizard pages, VisualGDB Project Properties pages and any other GUI involved in reproducing the problem. This is critical for us to be able to reproduce the problem on our side.
You can read more about the best way to report VisualGDB issues in our problem reporting guidelines, If you do not wish to document the repro steps and save the screenshots, please consider recording a screen video instead and sending us a link to it.
Please note that many VisualGDB issues are caused by selecting an incompatible combination of settings at some point. We are generally not able to review specific projects and find the specific settings that were set incorrectly. We recommend checking the projects into source control and keeping a track of all changed settings to avoid breaking the projects.
You can also try checking various diagnostic output from various parts of VisualGDB as described on this page. Although we won’t be able to review it for a specific project unless the we can reproduce the problem from scratch, checking it might provide some clues on what is causing the unexpected behavior.
You must be logged in to reply to this topic.