Intellisense cannot find include file iso646.h

Sysprogs forums Forums VisualGDB Intellisense cannot find include file iso646.h

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #32055
    paulh001
    Participant

    Since I moved to the new OS on raspberry pi (bullseye) I have troubles with intellisense reporting that it cannot find include files.

    Specificly iso646.h Later you get a yellow bar in the screen with found package but this keeps appearing.

    Also switching between source files intellisence waiting for async message box popsup and you have to wait until it is finsihed.

    Is there a way to fix this?

    Also intellisense crashes all the time.

    • This topic was modified 2 years, 8 months ago by paulh001.
    Attachments:
    You must be logged in to view attached files.
    #32058
    support
    Keymaster

    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:

    1. The steps should begin with launching Visual Studio. They should include every step necessary to create the project from scratch and reproduce the issue.
    2. 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.
    3. 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.

    Another common cause of errors is updating to a new toolchain/BSP/SDK. Many of these components are maintained by device vendors or communities, and require minor adjustments to the project when switching to newer versions. If you have recently updated any of such components, please consider reverting back to the old version as described here. There is no need to downgrade VisualGDB itself, as it is updated separately from such components.

    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.

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.