Add Support for Stepping out of Code Blocks feature

[SougandhS]

Introduce a new debugger operation that allows users to step out of the current loop, conditional statement, or nested code block etc. The operation uses run-to-line to identify the first executable line after the enclosing block and is available through the keyboard shortcut (Shift+F7), toolbar, and debug context menus.

Working.mp4

Fixes #966

What it does

How to test

Author checklist

• I have thoroughly tested my changes
• The change is following the coding conventions
• I have signed the Eclipse Contributor Agreement (ECA)

[SougandhS]

Hi @iloveeclipse, can you trigger a co-pilot review ?

[Copilot]

🟡 Changes recommended

Target resolution can select incorrect or unrelated code locations, and the new test has a suspension-event race.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Adds a debugger command to step out of the current Java code block using run-to-line behavior.

Changes:

• Adds the Shift+F7 command, toolbar button, menus, and icon.
• Implements AST-based enclosing-block target resolution.
• Adds automated stepping coverage and a test program.

File summaries

File	Description
StepOutOfCodeBlockHandler.java	Implements command handling and enablement.
RunToLineAdapter.java	Adds block-exit target calculation.
plugin.xml	Registers command, menus, toolbar, and shortcut.
plugin.properties	Adds command labels.
stepOutBlock.svg	Adds toolbar icon.
AutomatedSuite.java	Registers the new test suite.
AbstractDebugTest.java	Adds the test program fixture.
StepOutOfCodeBlockTests.java	Tests block stepping behavior.
StepOutCodeBlockPgm.java	Provides stepping scenarios.

Review details

• Files reviewed: 8/9 changed files
• Comments generated: 6
• Review effort level: Balanced

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[SougandhS]

@iloveeclipse Do you have any suggestions ?

[SougandhS]

@iloveeclipse Do you have any suggestions ?

Im planning to include this in M1 If no further changes are required..

[Copilot]

Copilot review overview

🟡 Changes recommended

Several control-flow constructs can produce disabled actions or unreachable run-to-line targets.

Review effort: Balanced
Findings: 4

Open (4)

• Avoid synchronous reparsing during isEnabled evaluation · New
• Stop boundary search at lambda execution boundaries · New
• Handle non-fallthrough switch rule blocks · New
• Handle try statements as continuation boundaries · New

Resolved since last review (6)

• This uses the selected stack frame's line number against whichever editor happens to be active,…
• Using the body's closing brace as the boundary is incorrect for constructs whose syntax continues…
• The traversal recognizes a conditional/loop only through a Block body. For an unbraced construct…
• Target lookup in this helper is not bounded to the method or initializer containing the current…
• The enablement parser omits the preview-feature options used by the execution parser above. For…
• Every caller invokes the step-out command before constructing this waiter, but DebugEventWaiter…

[Copilot]

Copilot review overview

🟡 Changes recommended

Block detection misses valid constructs and the shared adapter regresses existing Run to Line error handling.

Review effort: Balanced
Findings: 1 · 1 · 1

Open (3)

• Preserve Run to Line failures outside block-step handling · New
• Use complete try statement as catch continuation boundary · New
• Rename command label to Step Out of Code Block · New

Resolved since last review (4)

• Handle try statements as continuation boundaries
• Handle non-fallthrough switch rule blocks
• Stop boundary search at lambda execution boundaries
• Avoid synchronous reparsing during isEnabled evaluation

[iloveeclipse]

@SougandhS : as JDT committer, you should be able to enable Copilot Enterprise for your github account and run Copilot reviewer by yourself. Would be great if you could just do it without waiting me to trigger that. You can do this on your Eclipse account https://accounts.eclipse.org/users/<your account name> , there under "Link GitHub Account" you can toggle "Opt in to GitHub Copilot Enterprise for Eclipse Committers" checkbox.

[SougandhS]

@SougandhS : as JDT committer, you should be able to enable Copilot Enterprise for your github account and run Copilot reviewer by yourself. Would be great if you could just do it without waiting me to trigger that. You can do this on your Eclipse account https://accounts.eclipse.org/users/<your account name> , there under "Link GitHub Account" you can toggle "Opt in to GitHub Copilot Enterprise for Eclipse Committers" checkbox.

Thanks Andrey, I thought this feature was only for JDT Leads. I have linked my account and toggled the option now 👍 .. Might take some time to reflect it in my profile

[iloveeclipse]

Might take some time to reflect it in my profile

I can't remember if there was anything special to switch in your github profile too, something like "enable AI" or so. Please double check https://github.com/settings/copilot/features. At the very top it should show something like this:

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[Copilot]

🟡 Changes recommended

Unbraced constructs and method-return fallback paths currently produce incorrect stepping behavior.

1 open finding

• Distinguish traversal errors from valid no-continuation results · New

1 resolved since last review

• Switch rule bodies are not recognized for exit stepping

🧠 Review effort: Balanced

[Copilot]

🟡 Changes recommended

Breakpoint lookup can select unreachable code inside a following local class declaration.

1 open finding

• Skip local class bodies when finding the next executable statement · New

1 resolved since last review

• Distinguish traversal errors from valid no-continuation results

🧠 Review effort: Balanced

[Copilot]

🟡 Changes recommended

Loop bodies followed by local classes can produce an unreachable run-to-line target.

1 open finding

• Find containing block before skipping following local class · New

1 resolved since last review

• Skip local class bodies when finding the next executable statement

🧠 Review effort: Balanced

[Copilot]

🟡 Changes recommended

The local-class traversal path lacks coverage, and invalid-target feedback incorrectly blames the editor selection.

1 open finding

• Add integration coverage for skipping following local classes · New

1 resolved since last review

• Find containing block before skipping following local class

Previously missed (1)

In code that hasn't changed since last review

Report when no valid step-out target exists

org.eclipse.jdt.debug.ui/​ui/​org/​eclipse/​jdt/​internal/​debug/​ui/​actions/​RunToLineAdapter.java:144

This message refers to a “selected line,” but block stepping ignores the editor selection and derives the request from the suspended frame. It is also used when a block exists but has no executable successor in the enclosing declaration, so the current wording incorrectly tells users that their selection is the problem. Report that no valid step-out target could be found instead.

🧠 Review effort: Balanced

[Copilot]

🟡 Changes recommended

Forward breakpoint lookup can incorrectly descend into a local class following a loop or synchronized block.

1 open finding

• Clarify missing exit location message for current execution point · New

1 resolved since last review

• Add integration coverage for skipping following local classes

🧠 Review effort: Balanced

---

Give feedback about Copilot approvals in this survey to enter a drawing for a $150 gift card.

[Copilot]

🟡 Changes recommended

Local classes following loop bodies can still produce unreachable run-to-line targets.

1 open finding

• Skip local classes after loop or synchronized bodies · New

1 resolved since last review

• Clarify missing exit location message for current execution point

🧠 Review effort: Balanced

---

Give feedback about Copilot approvals in this survey to enter a drawing for a $150 gift card.

[Copilot]

🟡 Changes recommended

Control-statement headers are not handled correctly, and the Java 23 tests are registered without runtime gating.

2 open findings

• Guard Java 23-dependent tests by runtime compatibility · New
• Skip local classes after loop or synchronized bodies

🧠 Review effort: Balanced

[Copilot]

🟡 Changes recommended

Block traversal can select unreachable branches and does not correctly handle unbraced constructs or some local-class successors.

2 open findings

• Avoid unreachable siblings when finding continuation lines · New
• Skip local classes after loop or synchronized bodies

1 resolved since last review

• Guard Java 23-dependent tests by runtime compatibility

🧠 Review effort: Balanced

[Copilot]

🔵 Needs a closer look

Block traversal still mishandles unbraced control statements and local classes following loop bodies.

2 open findings

• Avoid unreachable siblings when finding continuation lines
• Skip local classes after loop or synchronized bodies

🧠 Review effort: Balanced

[Copilot]

🟡 Changes recommended

Control-statement header suspension and nested local-type successors can produce missing or unreachable step-out targets.

1 open finding

• Avoid selecting unreachable lines inside local type declaration blocks · New

2 resolved since last review

• Avoid unreachable siblings when finding continuation lines
• Skip local classes after loop or synchronized bodies

🧠 Review effort: Balanced

[SougandhS]

I think most cases are handled now, and any rare edge cases that may have been missed can be addressed as they are reported.