Cannot open VisualGDB settings

Sysprogs forums Forums VisualGDB Cannot open VisualGDB settings

This topic contains 13 replies, has 2 voices, and was last updated by  support 1 month ago.

Viewing 14 posts - 1 through 14 (of 14 total)
  • Author
    Posts
  • #27476

    Lonko
    Participant

    We are using vgdb settings since ever and on some computers we cannot open these settings, because we get this error:

    VisualGDB version: 5.4.112.3309
    —————— System.NullReferenceException ——————
    System.NullReferenceException: Object reference not set to an instance of an object.
    at x9.get_MainExecutable()
    at VisualGDB.Common_GUI.Configuration_editors.ProjectPropertiesEditModel.LookupSettingsFile(iq a)
    at VisualGDB.Common_GUI.Configuration_editors.ProjectPropertiesEditModel..ctor(iq a, Boolean b)
    at VisualGDB.Common_GUI.Configuration_editors.MultipleProjectPropertiesEditModel.CreateConfigurationModel(iq a)
    at VisualGDB.Common_GUI.Configuration_editors.MultipleProjectPropertiesEditModel.g(a a)
    at VisualGDB.Common_GUI.Configuration_editors.MultipleProjectPropertiesEditModel..ctor(fs1 a)
    at s51.GDBProjectProperties.ExecuteForProject(s51 addIn, Object objPrj)

     

    We are using gnu make.

     

    Please help as the settings can be changed only on one PC now :/

    #27477

    support
    Keymaster

    Hi,

    It looks like your technical support has expired. We would be happy to help you resolve this, however we would kindly ask you to renew your technical support here first: https://sysprogs.com/splm/mykey

    #27478

    Lonko
    Participant

    Dear,

     

    support paid.

     

    BR,

    #27479

    support
    Keymaster

    Thanks for renewing your license. It looks like the project has not been fully loaded.

    Please try updating to VisualGDB 5.5 Preview 4 and let us know if the problem persists. If it does, please attach an updated stack trace and we will help you troubleshoot it.

    #27480

    Lonko
    Participant

    Nope still the same problem…

    Initializing assemblies: 16 msec
    Registering factories: 105 msec
    E:\yyy\xxx.vcxproj is a VisualGDB project. Loading VisualGDB…
    Initializing VisualGDB 5.5.4.3540
    Checking fonts/colors: 15 msec
    Level 2 initialization: 4733 msec
    Checking if a VisualGDB-based project is being loaded…: 5072 msec => Loading VisualGDB
    hiding coverage report viewer…
    Querying output window style…
    showing coverage report viewer…
    SysprogsSuggestedActionsProvider: creating tagger for C/C++…
    SysprogsSuggestedActionsProvider: Not a CppEngine source. Skipping SuggestedActionsSource creation
    RenameHighlightSmartTaggerProvider: creating tagger for C/C++…
    RenameHighlightSmartTaggerProvider: creating tagger for Output…
    Unexpected exception: Object reference not set to an instance of an object.
    —————— System.NullReferenceException ——————
    System.NullReferenceException: Object reference not set to an instance of an object.
    at ky1.get_MainExecutable()
    at VisualGDB.Common_GUI.Configuration_editors.ProjectPropertiesEditModel.LookupSettingsFile(fy1 a)
    at VisualGDB.Common_GUI.Configuration_editors.ProjectPropertiesEditModel..ctor(fy1 b, Boolean a, x92 c)
    at VisualGDB.Common_GUI.Configuration_editors.MultipleProjectPropertiesEditModel.CreateConfigurationModel(fy1 a)
    at VisualGDB.Common_GUI.Configuration_editors.MultipleProjectPropertiesEditModel.i(c a)
    at VisualGDB.Common_GUI.Configuration_editors.MultipleProjectPropertiesEditModel..ctor(zh2 a, x92 b)
    at VisualGDB.Common_GUI.WPF.ProjectPropertiesWindow3..ctor(zh2 prj, Type pageTypeToSelect)
    at q7.GDBProjectProperties.ExecuteForProject(q7 addIn, Object objPrj, Type pageTypeToSelect)

    #27481

    support
    Keymaster

    No problem, we will walk you through pinpointing it.

    First of all, please try creating a similar project (GNU Make, same toolchain/target) and check if the project properties window works for it. If not, please make sure you can create regular VC++ projects (i.e. have the VC++ components installed).

    If the newly created project works, please try opening the VS Project Properties (not VisualGDB Project Properties) for the project and check the NMake Settings page. Does the page appear properly and list the .vgdbsettings file as the primary output? If you cannot find anything suspicious, please attach a screenshot of the NMake Settings page and also the entire VS window having the problematic configuration selected, so that we could check for common issues.

    #27482

    Lonko
    Participant

    Dear,

     

    It works. But would really like to avoid creating a new project. Because on stationary pc it work on laptop it does not. I have tried installing same version on both. Tried installing a trial version to 3rd computer and the project failed to open. Can we debug somehow or enable more logging to see which setting is problematic?

     

    BR,

    #27483

    support
    Keymaster

    Please carefully read the second part of our previous reply. It describes exactly what to do if the newly created project works.

    #27489

    Lonko
    Participant

    Dear,

    VS Property page does not load for my problematic project. I’m attaching screen shot and my vcxproj file.

     

    BR,

     

    Attachments:
    You must be logged in to view attached files.
    #27494

    support
    Keymaster

    Hi,

    If the VS project properties don’t work either, the project file is unfortunately corrupt and VisualGDB won’t be able to use it either.

    Most likely, you have accidentally edited the file manually, breaking some parts required by VS or VisualGDB. As this is generally something outside of our control, unfortunately we cannot review the project file within our regular product support. Our best advice would be to try recreating the project. If this is a Makefile project, you can also create a dummy project of similar type and just copy the new .vcxproj and .filters files over the ones and re-add source files to the project. Most of the build settings are stored in the Makefiles anyway, so they won’t be reset.

    Also if you can confirm that the file corruption happens consistently as a result of using VisualGDB GUI, we will be happy to fix it, although we would need to know the exact steps to reproduce the problem on our side.

    #27495

    Lonko
    Participant

    Dear

     

    i have 6 or seven projects like this on my stationary computer it works it opens visualgdb settings file

    on my laptop which is a mirror unit it shows this error

     

    so why would it work on one pc (vs2013 and vs2019 both work) second pc it does not open??? What is machine specific?

    Can we debug and find out? Reluctant to create a new project for each. And i never edited this by hand for sure!

    BR

    #27496

    support
    Keymaster

    The only way to diagnose it is to create a new similar project from scratch and compare the .vcxproj and .filters files. You would need to make a list of changes, manually merge them between the files and recheck whether each of the changes fixes the issue. This could be time-consuming, there is no other way to pinpoint it and we are not able to do this for you, since this is not a project created by us. Depending on your constraints, simply re-creating the project could be faster.

    #27539

    Lonko
    Participant

    Dear,

     

    we created new project and now it works. This probably happenend as the projects are up to 4 years old at least.

     

    p.s. Which setting disables this???

    VisualGDB version: 5.5.4.3540
    —————— at2 ——————
    at2: Deployed item size () does not match the original item size (209632). If this is a false positive, try disabling deployment validation via global VisualGDB Settings. —> System.Exception: Deployed item size () does not match the original item size (209632). If this is a false positive, try disabling deployment validation via global VisualGDB Settings.
    at s01.e1(f11 b, List1 a)
    at s01.h1.c(f11 a)
    at o72.u
    1.g(f11 a)
    at VisualGDB.Add_In.Tool_Windows.WPF.DockedProgressPresenter.RunItemizedOperation(Action1 operation, String caption, ng exceptionHandler, String[] stages)
    at o72.y[_ResultType](gh1
    1 b, String c, Int32 a, String[] d)
    at s01.t1()
    — End of inner exception stack trace —
    at s01.t1()
    at s01.w1(DebugCustomizationSettings a, Boolean b)
    at e32.k2()
    at wo1.c2()
    at VisualGDB.GDBDebugEngine.f1(z71 a, p b)
    trace=[s01.t1:200, s01.w1:53, e32.k2:5442, wo1.c2:22, VisualGDB.GDBDebugEngine.f1:58]
    —————— Inner exception ——————
    —————— System.Exception ——————
    System.Exception: Deployed item size () does not match the original item size (209632). If this is a false positive, try disabling deployment validation via global VisualGDB Settings.
    at s01.e1(f11 b, List1 a)
    at s01.h1.c(f11 a)
    at o72.u
    1.g(f11 a)
    at VisualGDB.Add_In.Tool_Windows.WPF.DockedProgressPresenter.RunItemizedOperation(Action1 operation, String caption, ng exceptionHandler, String[] stages)
    at o72.y[_ResultType](gh1
    1 b, String c, Int32 a, String[] d)
    at s01.t1()
    trace=[s01.e1:1381, s01+h1.c:0, o72+u`1.g:0, VisualGDB.Add_In.Tool_Windows.WPF.DockedProgressPresenter.RunItemizedOperation:209, o72.y:92, s01.t1:123]

    #27542

    support
    Keymaster

    Hi,

    Please use the following page to search through all VisualGDB settings: https://visualgdb.com/settings/

    You can find the up-to-date setting name by searching for “deploy”. Please also make sure you are using this build, as the Preview 4 might apply the setting incorrectly in some cases: VisualGDB-5.5.4.3549.msi

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

You must be logged in to reply to this topic.