VisualDGB Exeption when want to run

Sysprogs forums Forums VisualGDB VisualDGB Exeption when want to run

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #33653
    jatr
    Participant

    I can not run my project. I installed the new version, and after that appear, the following error :

    VisualGDB version: 5.6.109.4777
    —————— System.NullReferenceException ——————
    System.NullReferenceException: Object reference not set to an instance of an object.
    at zx1..ctor(Dictionary`2 d, ConfiguredMCU b, ConfiguredDebugMethod a, z32 c, gz2 e)
    at z32..ctor(r32 a, ISettingsObjectWithDriverCheckSetting e, ConfiguredMCU d, Dictionary`2 c, ConfiguredDebugMethod b, String f)
    at vl1..ctor(r32 b, EmbeddedDebugSubsystemSettings f, vh1 a, r91 e, GDBSessionLaunchOptions d, ManagedToolchain c)
    at r91.h_2(r32 a, GDBSessionLaunchOptions b)
    at r32..ctor(VisualGDBProjectSettings2 d, e7 a, GDBSessionLaunchOptions c, wd2 e, Boolean b)
    at dn2..ctor(GDBSessionLaunchOptions a, d12 b)
    at d12..ctor(GDBSessionLaunchOptions a)
    at a13.g(s8 a)
    at VisualGDB.GDBDebugEngine.w(q03 a)
    at VisualGDB.GDBDebugEngine.Attach(IDebugProgram2[] e, IDebugProgramNode2[] c, UInt32 a, IDebugEventCallback2 d, enum_ATTACH_REASON b)
    trace=[zx1..ctor:108, z32..ctor:35, vl1..ctor:198, r91.h_2:44, r32..ctor:125, dn2..ctor:872, d12..ctor:82, a13.g:117, VisualGDB.GDBDebugEngine.w:99, VisualGDB.GDBDebugEngine.Attach:32]

    I re-install Visual Studio 2019 and VisualGDB

    Regards

    Alberto

    #33655
    support
    Keymaster

    Hi,

    This looks like the project you are trying to debug is referencing a non-existent debug method. Please try opening VisualGDB Project Properties and double-check the debug settings there. If VisualGDB suggests installing missing packages (e.g. OpenOCD), please proceed with installing them.

    P.S. VisualGDB was supposed to show a more informative error message in this case, but due to a bug it reverted to a rather generic one. We have fixed it on our side and will include the fix in the next maintenance release.

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