Debugger doesn't stop at breakpoint inside finally block when no exception raised

[vitalyla]

In a regular Java application, when a breakpoint is set within the finally block, the debugger session doesn’t terminate there when no exception is raised.

However, if an exception is raised during the execution of the code, the debugger will stop at the breakpoint.

[vitalyla]

Here’s an additional update on the case. When using stepped debugging (i.e., pressing F10), the breakpoint under the “finally” block is reached. However, when pressing F5, the breakpoint in the “finally” block is not engaged. The block does get executed, but the breakpoint is not activated when pressing F5 in normal execution flow.

Vitaly

[github-actions]

Hi @vitalyla, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

Couldn’t find a built-in workaround for breakpoints in finally blocks on normal (no-exception) exits. It appears to be a runtime/source-mapping limitation in the Java debugger extension. You can

• Verify your source lookup settings (missing/mismatched .class ↔ .java mapping will skip your breakpoint):
– #1364 (comment)

If the problem persists, please open a new issue in the Java Debug repo with a minimal reproduction.

Other references with low confidence

• VSCode java Debugger ignores breakpoints and instead breaking in platform classes
  Breakpoints sometimes get skipped and the debugger jumps to the first frame with valid source.
  VSCode java Debugger (v0.52.0) ignores break points and instead breaking in platform classes for now reason #1364 (comment)

• Breakpoints are skipped unless they are in the debugged class itself
  Breakpoints in called classes may be ignored if the debugger isn’t correctly resolving modules or source paths.
  Breakpoints are skipped unless they are in the debugged class itself #1116

The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!