Step through

Steps over the current line and takes you to the next line even if the current line includes function calls. The calls are skipped, and you move straight to the next line of the caller.

If there are breakpoints inside the skipped methods, the debugger will stop at them. To skip any breakpoints on the way, use Force step over.

Steps inside the code of a called function.

Some methods are skipped by Step into as you normally might not need to debug them. This list can be fine-tuned on the Build, Execution, Deployment | Debugger | Stepping page of the Settings dialog () .

Smart step into is helpful when there are several method calls on a line, and you want to be specific about which method to enter. This feature allows you to select the method call you are interested in.

warning

This feature is not applicable to C/C++ debugging. However, you can use it for other languages like JavaScript and Python.

You can configure Smart Step Into to be used instead of the regular Step Into every time there are multiple method calls on the line. This is done in Settings | Build, Execution, Deployment | Debugger | Stepping.

Steps out of the current function and takes you to the code of the caller.

Continues the execution until the position of the caret is reached.

1. Place the caret at the line where you want the program to pause.

2. Select Run to Cursor from the menu or press .

Also, you can Run to Cursor by hovering over the line and clicking the Run to Cursor icon.

You can configure whether you want Run to Cursor to work on clicking a line number in Settings | Build, Execution, Deployment | Debugger.

To skip any breakpoints on the way, use Force run to cursor.

Steps into the function even if it is skipped by the regular Step Into by default.

In case the source code of the function that you want to step into is unavailable, you can debug disassembled code in a dedicated view.

static void count(int to) {
    for (int i = 0; i < to; i++) {
        // the program is suspended here
            System.out.println(i);
        }
    System.out.println("Complete!");
}

public void println(String x) {
    // Force Step Into enters the implementation of PrintStream.println()
    if (getClass() == PrintStream.class) {
        writeln(String.valueOf(x));
    } else {
        synchronized (this) {
            print(x);
            newLine();
        }
    }
}

Continues the execution until the position of the caret is reached. All breakpoints on the way are ignored.

Steps over the current line of code and takes you to the next line even if the current line has method calls in it. If there are breakpoints in the called methods, they are ignored.

Although reversible debugging is not supported in CLion out-of-the-box, you can set it up on Linux using the Undo plugin.

The plugin integrates the Undo ’s record, rewind and replay technology in CLion. With Undo, you can record the program’s execution down to single instruction for further replay and analysis. This way, the debugger gets reversible: you can step forwards and backwards in your code and see exactly what is happening.

Read this blog post and watch this webinar recording for more information.