Can't launch VisualGDB debugger

Sysprogs forums Forums VisualGDB Can't launch VisualGDB debugger

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #33061
    mattia
    Participant

    Hello,

    after I moved to 5.6R7 I am unable to debug an old project: I get this message in diagnostics:

    ShouldRedirectToVisualGDBImpl(): C:\Work\Progetti\_SOURCE\15_Firmware\FW00018-FW_APP_REMSMPC_HMI4.3_V01\03_SourceApp\FW00018-FW_APP_REMSMPC_HMI4.3_V01\FW00018-FW_APP_REMSMPC_HMI4.3_V01-Debug.vgdbsettings vgdb://TargetPath=C:\Work\Progetti\_SOURCE\15_Firmware\FW00018-FW_APP_REMSMPC_HMI4.3_V01\03_SourceApp\FW00018-FW_APP_REMSMPC_HMI4.3_V01\VisualGDB\Debug\FW00018-FW_APP_REMSMPC_HMI4.3_V01
    Found RTOS in C:\Work\Progetti\_SOURCE\15_Firmware\FW00018-FW_APP_REMSMPC_HMI4.3_V01\03_SourceApp\FW00018-FW_APP_REMSMPC_HMI4.3_V01\VisualGDB\Debug\FW00018-FW_APP_REMSMPC_HMI4.3_V01: FreeRTOS
    gdb session initialization failed at stage 7: ------------------ System.ArgumentNullException ------------------
    System.ArgumentNullException: Il valore non può essere null.
    Nome parametro: source
    in System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
    in l53.i1()
    in l53..ctor(EmbeddedTimestampProvider a, Double c, Dispatcher b)
    in jt2..ctor(c4 a, EmbeddedDebugSubsystemSettings b, vs1 f, ge2 c, GDBSessionLaunchOptions d, ManagedToolchain e)
    in ge2.g_2(c4 b, GDBSessionLaunchOptions a)
    in c4..ctor(VisualGDBProjectSettings2 c, hp d, GDBSessionLaunchOptions a, zg3 b, Boolean e)
    in h82..ctor(GDBSessionLaunchOptions b, tc2 a)
    trace=[System.Linq.Enumerable.ToArray:3, l53.i1:0, l53..ctor:53, jt2..ctor:1275, ge2.g_2:76, c4..ctor:125, h82..ctor:332]
    
    Unexpected exception: ------------------ System.ArgumentNullException ------------------
    System.ArgumentNullException: Il valore non può essere null.
    Nome parametro: source
    in System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
    in l53.i1()
    in l53..ctor(EmbeddedTimestampProvider a, Double c, Dispatcher b)
    in jt2..ctor(c4 a, EmbeddedDebugSubsystemSettings b, vs1 f, ge2 c, GDBSessionLaunchOptions d, ManagedToolchain e)
    in ge2.g_2(c4 b, GDBSessionLaunchOptions a)
    in c4..ctor(VisualGDBProjectSettings2 c, hp d, GDBSessionLaunchOptions a, zg3 b, Boolean e)
    in h82..ctor(GDBSessionLaunchOptions b, tc2 a)
    in tc2..ctor(GDBSessionLaunchOptions a)
    in yl3.b_2(xk1 a)
    in VisualGDB.GDBDebugEngine.Attach(IDebugProgram2[] e, IDebugProgramNode2[] a, UInt32 c, IDebugEventCallback2 d, enum_ATTACH_REASON b)
    trace=[System.Linq.Enumerable.ToArray:3, l53.i1:0, l53..ctor:53, jt2..ctor:1275, ge2.g_2:76, c4..ctor:125, h82..ctor:872, tc2..ctor:90, yl3.b_2:129, VisualGDB.GDBDebugEngine.Attach:32]

     

    And I can’t debug it anymore. I tried a new project, and it works without any problems.

    Is it related to the new version?

    Thank you,

    Mattia Berton

    #33066
    support
    Keymaster

    Sorry about that, it’s indeed a bug introduced by another fix in v5.6R7. We have fixed it in the following build: VisualGDB-5.6.107.4696.msi

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