VisualGDB initially setting incorrect source path for breakpoint

Sysprogs forums Forums VisualGDB VisualGDB initially setting incorrect source path for breakpoint

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

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #33227

    Lonko
    Participant

    Dear,

    we use Visualgdb in a way that we cross compile app on remote build server and “deploy to target”, deployment never happens as the target has mounted nfs share. So we just provide the path and select never copy: picture 1. (showing only how the target is set, but while debugging this is set to never)

    Once the project builds and project debug starts we get notification that all breakpoints are pending and breakpoint main is set. Like it cannot find the source file. Then the Path diagnose popups picture 2. and if I only press next in the dialog for path diagnose i can see in the backround that breakpoints lit up and are hittable.

    Attaching the visualgdb log from session.

    In the log prior to diagnose paths breakpoints are set in ProjectDir/Debug/src/…. anfter diagnose they are moved to ProjectDir/src/….source files.

    Why ? is the project config wrong or is this somekind of bug?

     

    BR,

     

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

    support
    Keymaster

    Unfortunately, it is hard to suggest anything specific based on the description you provided.
    In order for us to provide any help with this, we need to be able to reproduce the problem on our side.
    Please provide complete and detailed steps to reproduce the issue as described below:

    1. The steps should begin with launching Visual Studio. They should include every step necessary to create the project from scratch and reproduce the issue.
    2. Please make sure the steps do not involve any 3rd-party code as we will not be able to review it. If the problem only happens with a specific project, please make sure you can reproduce it on a clean project created from scratch.
    3. The steps should include uncropped screenshots of all wizard pages, VisualGDB Project Properties pages and any other GUI involved in reproducing the problem. This is critical for us to be able to reproduce the problem on our side.

    You can read more about the best way to report VisualGDB issues in our problem reporting guidelines, If you do not wish to document the repro steps and save the screenshots, please consider recording a screen video instead and sending us a link to it.

    Please note that many VisualGDB issues are caused by selecting an incompatible combination of settings at some point. We are generally not able to review specific projects and find the specific settings that were set incorrectly. We recommend checking the projects into source control and keeping a track of all changed settings to avoid breaking the projects.

    We would also kindly ask you to renew your support as it has expired a few months ago.

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

You must be logged in to reply to this topic.