VSCode debugger conditional breakpoints

With VSCode 1.52 (Nov. 2020), you also have:

Breakpoints View: Conditions for exception breakpoints

We now support editing conditions for Exception breakpoints from the BREAKPOINTS view using the "Edit Condition" context menu action.

For now, only the Mock Debug extension has a (fake) Exception Breakpoint condition support, but soon other debug extensions will follow - such as the Javascript debugger.

Edit Condition -- https://media.githubusercontent.com/media/microsoft/vscode-docs/vnext/release-notes/images/1_52/edit-condition.png

Exception Condition -- https://media.githubusercontent.com/media/microsoft/vscode-docs/vnext/release-notes/images/1_52/exception-condition.png

That applies to Node debugger in VSCode 1.53 (Jan. 2021): see issue 104453

conditional breakpoint

It is now possible to edit conditions for exception breakpoints and function breakpoints using the inline Edit Condition action or the new context menu actions.

Using conditions it is possible for the user to specify that the program should break on an exception only when a particular condition is met.

Currently the Javascript debug extension support conditions for exception or function breakpoints and soon other debug extensions will support it as well.

Breakpoint zone widget colored -- https://media.githubusercontent.com/media/microsoft/vscode-docs/56b62268c9df79ae72305b364eb18f4f4b4cc9bb/release-notes/images/1_53/breakpoints.gif

VSCode 1.55 (March 2021) will add:

Inline menu to edit condition and hit count

We now show an inline menu for editing conditions and hit counts for function breakpoints.
Previously the inline edit button would choose automatically what condition to edit, now the menu should make the flow easier and give more control to the user.

breakpoint condition menu

Access types of data breakpoints

Data breakpoints now support more access types to break on:

  • Break on Read: breakpoint will be hit every time a variable gets read.
  • Break on Access: breakpoint will be hit every time a variable is accessed.

As a reminder, data breakpoints can be added from a context menu in the VARIABLES view and we already supported Break on Value Change.

For now, only the Mock Debug extension has (fake) Data Breakpoint support for all three access types, but soon other debug extensions will follow - such as the Java extension.

break on access types


Yes, this is described in detail in the VS Code Debugging docs

In short, right click on an existing breakpoint and select "Edit breakpoint", or right click on the breakpoint margin and select "Add conditional breakpoint".

Tags:

Visual Studio Code

Related

Replace all instances of character in string in typescript? Found two getters or fields with conflicting case sensitivity for property IntelliJ IDEA 2017.1 does not stop on breakpoints How to test a TextField Material-UI element with React Jest? Should I remove leak canary code/classes for release build? Sampling without replacement from a given non-uniform distribution in TensorFlow How can I see Dockerfile for each docker image? How to check if a value is not null and not empty string in JS Measure runtime of a Jupyter Notebook code cell Auto errors detection in IntelliJ IDEA Angular testing how to prevent ngOnInit call to test a method directly Error: formControlName must be used with a parent formGroup directive. You'll want to add a formGroup directive - Angular reactive forms

Recent Posts