Sysprogs forums Forums VisualGDB intellisense

This topic contains 3 replies, has 2 voices, and was last updated by  support 1 year, 3 months ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
  • #32973


    I keep having a lot of issues with IntelliSense. I am developing for raspberry PI linux.

    Intellisense is adding the wrong include directories to the project and or is not parsing standard c++ include files like <chrono>, <string> etc.

    Also I pressed the red cross to stop adding the wrong include file directories, but I cannot find a menu item to restart Intellisense to start scanning again.

    Intellisense adds /usr/include/aarch64-linux-gnu;/usr/include/aarch64-linux-gnu/c++/10;/usr/include/c++/10/tr1;/usr/include/linux to the project, after this the project does not compile any more


    C:\Users\paulh\OneDrive\source\Test5 => /tmp/VisualGDB/c/Users/paulh/OneDrive/source/Test5: 1 files copied (253 bytes).
    Run “ninja -f “VisualGDB/Debug/Test5.msbuild-ninja”” in directory “/tmp/VisualGDB/c/Users/paulh/OneDrive/source/Test5” on pi@ (SSH)
    ninja -f “VisualGDB/Debug/Test5.msbuild-ninja”

    [0/2] Test5.cpp
    [1/2] Test5.cpp
    FAILED: VisualGDB/Debug/Test5.o
    g++ @VisualGDB/Debug/Test5.gcc.rsp -c “Test5.cpp” -o “VisualGDB/Debug/Test5.o” -MD -MP -MF “VisualGDB/Debug/Test5.o.dep”
    In file included from /usr/include/c++/10/bits/postypes.h:40,
    from /usr/include/c++/10/iosfwd:40,
    from /usr/include/c++/10/ios:38,
    from /usr/include/c++/10/ostream:38,
    from /usr/include/c++/10/iostream:39,
    from Test5.cpp:1:
    /usr/include/c++/10/tr1/cwchar:45:14: error: ‘wcstof’ has not been declared in ‘std’
    45 | using std::wcstof;
    | ^~~~~~
    /usr/include/c++/10/tr1/cwchar:48:14: error: ‘vfwscanf’ has not been declared in ‘std’
    48 | using std::vfwscanf;
    | ^~~~~~~~
    /usr/include/c++/10/tr1/cwchar:51:14: error: ‘vswscanf’ has not been declared in ‘std’
    51 | using std::vswscanf;
    | ^~~~~~~~
    /usr/include/c++/10/tr1/cwchar:54:14: error: ‘vwscanf’ has not been declared in ‘std’
    54 | using std::vwscanf;
    | ^~~~~~~
    /usr/include/c++/10/tr1/cwchar:58:14: error: ‘wcstold’ has not been declared in ‘std’
    58 | using std::wcstold;
    | ^~~~~~~
    /usr/include/c++/10/tr1/cwchar:59:14: error: ‘wcstoll’ has not been declared in ‘std’
    59 | using std::wcstoll;
    | ^~~~~~~
    /usr/include/c++/10/tr1/cwchar:60:14: error: ‘wcstoull’ has not been declared in ‘std’
    60 | using std::wcstoull;

    I use bullseye OS and a new installation of the operating system.

    Any advise for this issue?

    You must be logged in to view attached files.



    Based on the screenshots you provided, the build also fails. So it looks like a corrupt build environment and not a VisualGDB IntelliSense issue.



    The build fails because intellisense has added incorrect include directories. When I remove these it compiles. The question is why is intellisense adding incorrect include directories? If I remove these include directories. Intellisense directly tries to add them again.



    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.

    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 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.