Debug Goto Statement Visual Studio

Question

Debug Goto Statement Visual Studio

Sid Kraft 101

Using Visual Studio, C++ with the debugger, how does one "branch" to a particular statement in the code? Sid Kraft

Durga Ram 0 Reputation points

2026-05-17T06:16:40.5233333+00:00

// DEBUGGER NOTE: If you need to skip the validation logic above during testing,

// right-click the line below and select 'Set Next Statement' (Ctrl+Shift+F10).

int targetStatement = 10

;

2 answers

Your answer

Durga Ram 0 Reputation points

2026-05-17T06:16:40.5233333+00:00

// DEBUGGER NOTE: If you need to skip the validation logic above during testing,

// right-click the line below and select 'Set Next Statement' (Ctrl+Shift+F10).

int targetStatement = 10

;

Answer 1

In C++ code running under the Visual Studio debugger, execution cannot be arbitrarily “branched” to an arbitrary source line from the debugger UI. The debugger supports:

Setting breakpoints on the line where execution should pause, then continuing with F5 so the program runs normally until that point.
Using step commands (F10, F11) to move through code one statement at a time.

To transfer control inside the program logic itself, the C++ language provides the goto statement:

void func()
{
    // ... some code ...

    goto target;  // unconditional branch

    // code skipped by goto

target:
    // execution continues here
}

Rules for goto in C++:

The label must be in the same function as the goto.
goto cannot jump forward over the initialization of a variable that would be in scope at the destination.
It is generally recommended to use break, continue, and return instead of goto when possible.

So, to “branch” while debugging:

Use breakpoints and stepping in the debugger to control where execution stops and how it advances.
Use goto labels in the C++ code itself if an unconditional jump within a function is required by the program logic.

References:

Answer 2

RLWA32 52,831

Have a look at the VS Debugger's ability to set the next statement to be executed Move the execution pointer to change the execution flow in the debugger

0 comments