visual GDB Clang/Intellisense stops working

Sysprogs forums Forums VisualGDB visual GDB Clang/Intellisense stops working

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

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

    b.timofte
    Participant

    Dear all

    I have the file bellow in a Cmake project

    #pragma once

    #include <boost/log/core.hpp>
    #include <boost/log/trivial.hpp>
    #include <boost/log/expressions.hpp>

    namespace logging = boost::log;

    typedef enum logLevels
    {

    } logLevels;

    class LoggerClass
    {
    public:
    LoggerClass()
    {
    }

    void init()
    {
    logging::core::get()->set_filter(logging::trivial::severity >= logging::trivial::info);
    }

    };

     

    I observe Clang intellisense go to definition randomly stops working and the code colors dissapear . Modifying the file or/annd invoking itellisense via member enumeration or autocompletion will freeze VS2017 for UP tp 1 minute . Any change in this file basically freezes down the editor

     

    Any idea where is the bug ?

     

    #21608

    b.timofte
    Participant

    I attached a screenshot with the freeze for example when refactoring

     

    [+0:39:56.360] Checked xxx\logger.h: 18 error records
    [+0:39:56.440] Found entity at cursor location: @ZN11LoggerClass8logerrorESs [ LoggerClass::logerror(std::string)] (f)
    [+0:39:56.440] Operation completed: Parse – Goto [38919 msec]

     

     

    • This reply was modified 3 months, 1 week ago by  b.timofte.
    Attachments:
    You must be logged in to view attached files.
    #21611

    b.timofte
    Participant

    [+0:44:22.820] Opening brace typed: bracket matching enabled, this occurence will be processed
    [+0:44:22.820] Starting operation: Parse – HighlightBraces
    [+0:44:22.820] Operation completed: Parse – HighlightBraces [0 msec]
    [+0:44:25.994] Starting operation: Parse – HighlightBraces
    [+0:44:25.994] Operation completed: Parse – HighlightBraces [0 msec]
    [+0:44:26.431] Starting operation: Parse – QuickInfo
    [+0:44:27.273] Starting operation: Reformatting text
    [+0:44:27.273] Operation completed: Reformatting text [0 msec]
    [+0:44:45.617] Value does not fall within the expected range. while trying to build data tip
    [+0:44:45.617] Stack trace:
    [+0:44:45.617]     Server stack trace:
    [+0:44:45.617]        at je1.f(wx1& c, f91 a, String b)
    [+0:44:45.617]        at cg1.t(wx1 a, String b, Boolean d, Int32 c)
    [+0:44:45.617]        at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
    [+0:44:45.617]        at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)
    [+0:44:45.617]     Exception rethrown at [0]:
    [+0:44:45.617]        at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
    [+0:44:45.617]        at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
    [+0:44:45.617]        at cg1.t(wx1 a, String b, Boolean d, Int32 c)
    [+0:44:45.617]        at cp1.e1.h(tn a)
    [+0:44:45.617]        at sa11.o1.b()
    [+0:44:45.617]        at be2.a.c_2[_Ty](b`1 a)
    [+0:44:45.617]        at sa11.c[_ReturnTy](l2 b, k52 a)

    #21620

    support
    Keymaster

     

    Hi,

    It looks like it takes VisualGDB over 30 seconds to parse the source file. It could be expected first time you parse a file with many includes (Boost would be a perfect example of that), but then VisualGDB should cache the header file contents and the subsequent operations should be much faster.

    Also the refactoring should normally show the “Searching for references” window while it analyzes the source. It is by design that this window blocks the reset of the Visual Studio GUI as editing the code while it is being analyzed would lead to unpredictable results.

    The last log snippet looks like VisualGDB fails to properly display a popup hint for some part of the code. It should not cause any slowdown or any other issues and can be safely ignored. If it looks like VisualGDB consistently doesn’t show a popup for some code where it should work, please let us know the repro steps and we will investigate it.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.