See Also

Use this page to configure capture points to facilitate debugging of asynchronous code.

A capture point is a place in your code where the debugger captures staktraces to be used later when you reach a specific point in the code (the insertion point) and want to see how you got there. IntelliJ IDEA does this by substituting part of the call stack with a captured stack.

For more information on asynchronous debugging refer to Debugging Asynchronous flow.

You can download most common capture settings from the following repository: IntelliJ IDEA debugger Capture Points.

ItemDescription
images/new.png Click this icon to configure a new capture point. Fill in the following information:
  • Capture class name: enter the name of the class at the top of the stack trace you want to capture.
  • Capture method name: enter the name of the method at the top of the stack trace you want to capture.
  • Capture key expression: enter the capture key expression. The capture key expression is evaluated and the value is used as the key.
  • Insert class name: enter the name of the class where you want to insert the captured stack trace.
  • Insert method name: enter the name of the method where you want to insert the captured stack trace.
  • Insert key expression: enter the key expression that will be evaluated and this value will be matched with the key in the captured stack.

Use the checkbox next to each entry to enable/disable the selected capture point.

images/delete.png Click this icon to remove the capture point from the list.
images/arrowUp.pngimages/arrowDown.png Click these icons to move the selected item one line up or down in the list.
images/copy.gif Click this icon to duplicate the selected entry.
images/ImportCaptureSettings.png Click this icon to import capture point settings from a file.
images/ExportCaptureSettings.png Click this icon to export capture point settings to a file.
Capture local variables Select this option if you also want to capture local variables (primitives and String values) together with the call stack. Note that this may sufficiently slow down the debugging process.

See Also

Procedures:

Concepts: