WANT TO DEBUGG TwinCAT/BSD ON VS2022 USING VISUALGDB

Sysprogs forums Forums VisualGDB WANT TO DEBUGG TwinCAT/BSD ON VS2022 USING VISUALGDB

Tagged: 

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #36552
    iamashish
    Participant

    I want to debug my TwinCAT/BSD machine on my windows pc remotely using visual studios 2022
    so the flow goes like this i have the source code with executable in my window pc and i copied the executable in my TwinCAT/BSD  machine and debugg from my local pc using vs 2022
    So is it possible to debug using VisualGDB . But one condition source  code should not be copied or transferred to TwinCAT/BSD  machine
    If there is a way please help me with the setup

    Thank You in Advance

    #36554
    iamashish
    Participant

    Is it possible to Debugg remote FreeBSD machine having source code in my local pc and executable in remote machine  ??

    #36556
    support
    Keymaster

    Hi,

    You can try using the Quick Debug feature. You can point it to the gdb executable and the debugged executable on the FreeBSD machine, and then configure source path mappings to help it locate the sources on the Windows machine.

    That said, FreeBSD debugging is not 100% compatible with Linux and we do not regularly test VisualGDB with FreeBSD due to a much smaller number of users. Most common functionality should work fine, but there might be glitches here and there.

    #36557
    iamashish
    Participant

    Thank You so much for the response

    I will try this and if any error occur try to solve it if not I will let you know if related to VisualGDB

    #36586
    iamashish
    Participant

    So i loaded the project and started the debugging . Debugging is working Perfectly fine but the issue is during debugging the mapping of some files is not correct the breakpoint is not hitting there showing mapping issue  is there a way I can solve this issue  ?

    Attachments:
    You must be logged in to view attached files.
    #36624
    support
    Keymaster

    Hi,

    This could be a bug in the gdb, or some quirks of the build system that might be solvable with path substitutions, but you would need to understand what path format would work with the underlying debugger.

    We would advise first getting a simple breakpoint to work by running gdb manually and experimenting with different path formats. Once this works, configuring VisualGDB to use the same path syntax should be straight-forward. If not, let us know the path format that works manually, and we will help you configure VisualGDB to use it.

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