CLion 2023.2 Help

Examine suspended program

After the debugger session has started, the Debug tool window will appear, and the program will run normally until one of the following happens:

After that, the program is suspended, allowing you to examine its current state, control its further execution, and test various scenarios at runtime.

Frames and threads

The state of the program is represented by frames. When the program is suspended, the current frame stack is displayed in the Frames pane.

Frames tab of the Debug tool window

A frame corresponds to the active method or function call. It stores the local variables of the called method or function, its arguments, and the code context that enables expression evaluation.

Each time a method is called, a new frame is added to the top of the stack. When the execution of a method is complete, the corresponding frame is removed from the stack (in the last in, first out fashion).

Examining frames helps you understand why particular parameters were passed to a method and what the state of the caller was at the time of calling.

Module names

There are cases where the code can be compiled to different modules, like template functions. You can learn in which binary the code is being executed at any moment from module names.

  • Right-click anywhere in the Frames pane and select Show Module Name:

    Frames context options

    Modules names will be shown for each of the stack frame entries:

    Module names

Threads

You can navigate through the list of the application threads. The ID given by the OS on thread start can help you identify the thread you are interested in:

Thread switcher

Thread Icons

Icons near each thread indicate the status of the thread relative to the current debugging session.

Icon

Description

Current thread

The current thread in suspended state.

Suspended thread

A suspended thread. Threads are marked as suspended when they were paused by the debugger.

Free/unfreeze individual threads

In CLion, you can suspend and resume threads while debugging.

Use the context menu in the thread view of the Debug tool window or Run | Debugging Actions on the main menu:

Freeze/unfreeze threads in the context menu
  • Freeze ... and Unfreeze ... – freezes and unfreezes the currently selected thread.

  • Freeze Other Threads – freezes all other threads except the currently selected one and unfreezes the currently selected thread if it was frozen before.

  • Unfreeze All Threads – resumes execution in all threads.

Copy stack to clipboard

  • To copy the call stack for the current thread, right-click anywhere on the Frames pane and select Copy Stack.

Explore and edit variables

The Variables pane shows the list of the variables in the selected frame/thread. Examining the variables can help you understand why the program operates in a certain way.

Variables pane

View variables in a dedicated dialog

CLion allows you to inspect variables in a dedicated dialog. This is useful when you need to keep track of some variable (or the object whose reference it holds) and at the same time be able to navigate between frames and threads.

  • Right-click a variable or a watch and select Inspect.

    Inspect dialog

Set variable values

If you want to test how the program would behave in certain conditions or fix its current behavior at runtime, you can do that by setting/changing the variable values.

  1. Select a variable and press F2. Alternatively, select Set Value from the context menu.

  2. Enter the value for the variable and press Enter.

    Enter new value

Alternatively, you can set a variable value using the inline hint popup. Click the hint that corresponds to the desired variable, expand the tree if required, and select Set Value:

Inline hint menu

View as array

The View as array action adds a watchpoint that renders a pointer value as array.

  • Select View as Array from the context menu of a pointer variable.

Specify the array size:

Specifying the size of the array

The array representation of the selected pointer will be added to the list or variables:

Viewing a pointer as array

If you need to look into the source code where some variable or class is declared, you can move there right from the Variables pane.

  • To navigate to the code where the variable is declared, right-click the variable and select Jump to Source F4.

  • To navigate to the class declaration of the variable type, right-click the variable and select Jump to Type Source Shift+F4.

Evaluate expressions

CLion lets you evaluate expressions during a debugging session to obtain additional details about the program state or test various scenarios at runtime.

Evaluate a simple expression in the editor

To quickly evaluate an expression, point at it in the editor. Note that function calls cannot be evaluated this way.

  1. Point at the expression you want to evaluate. The result of the expression appears in a tooltip.

    Value tooltip
  2. To view child elements of the resulting object, click the Expand button or press Control+F1.

    Viewing child elements inside the value tooltip

If you find value tooltips distracting, you can increase the delay or disable them altogether. To do this, in the Settings dialog (Control+Alt+S), go to Build, Execution, Deployment | Debugger | Data Views and set the Show value tooltip and Value tooltip delay options as required.

Evaluate a complex expression in the editor

If you want to evaluate an expression in the code that involves a method call, or you want to be specific about which portion of expression to evaluate, use the Quick Evaluate Expression option.

  1. Place the caret at the expression (to evaluate the closest matching expression) or select a portion of it (if you want to be specific about which part of a complex expression to evaluate).

  2. Click Run | Debugging Actions | Quick Evaluate Expression Control+Alt+F8. Alternatively, hold Alt and click the selection.

    Quick Evaluate Expression

You can configure Quick Evaluate to work for a piece of code on just selecting it (without using the menu/shortcut). Use this option carefully, as you can accidentally call methods when it is enabled.

To configure Quick Evaluate on code selection, go to Settings | Build, Execution, Deployment | Debugger | Data Views and set the Show value tooltip on code selection option as preferred.

Evaluate arbitrary expressions

Evaluating arbitrary expressions is the most flexible evaluating option. It lets you evaluate any code as long as it is in the context of the current frame. Using it, you can evaluate declarations, method calls, anonymous classes, lambdas, loops, and so on.

Use this feature to get additional information about the current state of the program and test various scenarios all within the same debugging session. This saves a lot of time by reducing the number of sessions you have to run.

  1. If you want to start with some expression or a variable, which is currently in front of you (for example, in the editor or on the Variables pane), select it.

  2. Click Run | Debugging Actions | Evaluate Expression Alt+F8. The shortcut may not work on Ubuntu (for correct operation, adjust the shortcut configuration).

  3. In the Evaluate dialog, modify the selected expression or enter a new one in the Expression field. Click Expand Shift+Enter to modify a multiline code fragment.

  4. Click Evaluate (Control+Enter for multiline mode). The expression result appears in the Result field.

    Evaluate expression dialog

    The result of the expression is taken from the return statement. When there is no return statement, the result is taken from the last line of code (it does not even have to be an expression: a single literal works too). When there is no valid line to take the value from, the result is undefined. If the specified expression cannot be evaluated, the Result field indicates the reason.

The Evaluate dialog is non-modal, so you can switch the focus back to the editor to copy other variables and expressions. You can also open multiple Evaluate dialogs if necessary.

View values inline

CLion shows the values of the variables right next to their usage. Once the variable value has changed, the inline view is updated with the new value and changes its color.

You can click an inline hint and expand it to examine the fields belonging to the variable. From this popup, you can also change the variable values and add inline watches.

Inline variables view

The inline view is enabled by default. To turn it off, in the Settings dialog (Control+Alt+S), go to Build, Execution, Deployment | Debugger | Data Views and disable the Show values inline option.

Add an Inline Watch

If you want the result of some expression to appear on a particular line, you can set up an inline watch for that. Inline watches are persistent and remain active after session restart.

  1. Click the inline hint referring to the object whose field you want to track.

  2. In the popup, select the field and click Add as Inline Watch.

    Adding an inline watch option
  3. Fine-tune the watch if needed. You can use any valid expression as a watch.

    Setting an inline watch
  4. Press Enter and the inline watch will appear on the same line:

    Inline watch

Inline watches you set in the editor are also shown under Inline Watches in the Variables pane of the Debug tool window:

Inline watch in the editor and in the Debug tool window

To remove an inline watch, hover over the watch and click the cross near it.

Watches

If you want to keep track of some variable or the result of a more complex expression, set up a watch for this variable or expression. This is useful when you need to evaluate something that is not regularly displayed on the list of variables, or to pin some instance variable thus eliminating the need to expand the tree after each step.

Watches are evaluated in the context of the selected frame. Watches cannot be evaluated when they are out of context or when they fail to compile. If this is the case, the watch is marked with the error icon Error icon.

By default, watches are shown together with variables in the Variables pane. To hide/reveal the Watches pane, use the Separate watches option in the Layout Settingsthe Restore Layout button menu.

Add a watch

  • Enter the expression in the top part of the Variables pane, then click Add to Watches.

    The expression in the Variables tab

After you have added a variable/expression to Watches, it stays there and is evaluated for each step, providing you with the result in the current context.

Edit a watch

  • Right-click the desired watch and select Edit.

Delete a watch

  • To remove a single watch, right-click it and select Remove Watch. Alternatively, select the watch and press Delete on the Variables/ Watches pane.

  • To remove all watches, right-click anywhere on the Variables/ Watches pane and select Remove All Watches.

Watches allow for the same actions as variables do. For example, you can view them in a dedicated dialog or use them to navigate to the source code.

Watches are a part of your project. This means you can stop and rerun the debugging session without risk of losing them.

Return to the current execution point

Examining the program state involves navigating in code, and you often need to return to the place where your program is suspended.

Do one of the following:

  • Go to Run | Debugging Actions | Show Execution Point.

  • Press Alt+F10.

  • Click The Show Execution Point button on the stepping toolbar of the Debug tool window.

The current execution point is indicated with a blue line. The code at this line has not been executed yet.

Blue line indicating the current execution point
Last modified: 13 November 2023