Auto resume trigger breakpoints once hit

[SougandhS]

This PR introduces an option to resume the virtual machine execution once a trigger breakpoint is hit. This allows trigger breakpoints to act as barriers for other breakpoints, enabling less priority breakpoints to remain active without requiring them to be disabled.

Screens -


Once trigger is enabled then users will be able to choose 'Resume' , Selecting 'Resume' will also include 'Ignored' tag to breakpoint label


On debugging trigger wont suspend at breakpoint line, it will only suspend on next breakpoint

---

Fixes #614

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 @jukzi , could you pls check this when you have time..

[jukzi]

Hi @jukzi , could you pls check this when you have time..

Code looks fine. I am testing it, thanks for working on that!! And congrats to your Election.

[SougandhS]

Code looks fine. I am testing it, thanks for working on that!! And congrats to your Election.

Thank you so much @jukzi 😇👏

[jukzi]

It works almost like i wished it would.
I see a single unexpected behaviour:
Lets have a Resume point with a Condition. When i edit the Condition the Breakpoint disables its "Resume" behavior back to single thread (may be an existing bug):

Also i would like to see a "Toggle Trigger Point" in the context menu, which would "Resume" by default (debatable) :

[jukzi]

fix API error

[SougandhS]

When i edit the Condition the Breakpoint disables its "Resume" behavior back to single thread

Will check this

Also i would like to see a "Toggle Trigger Point" in the context menu, which would "Resume" by default (debatable) :

Sure 👍

[SougandhS]

Added additional handling for conditional-resume-triggerpoints

Once resume is enabled, resume based labels will be shown for condition options

Added toggling Trigger points from context menu (by default it will be Resume-Triggers)

[jukzi]

Take this example:

package p1;

public class TestResume {
public static void main(String[] args) throws InterruptedException {
	System.out.println("main");
	Thread thread = new Thread(TestResume::runAsync);
	thread.start(); // add Triggerpoint with condition=false
	thread.join();
}
public static void runAsync() {
	System.out.println("async"); // add breakpint
}
}

and add the breakpoint as in the comments:

I found two problems:
Error 1: The Triggerpoint stops the program (should not happen, its a Triggerpoint, not a Breakpoint)
Error 2: The program never ends - even if i press Resume(F8). Thats fatal

[SougandhS]

Take this example:

thanks for this example

Error 1: The Triggerpoint stops the program (should not happen, its a Triggerpoint, not a Breakpoint)
Error 2: The program never ends - even if i press Resume(F8). Thats fatal

fixed both now 👍

[eclipse-jdt-bot]

This pull request changes some projects for the first time in this development cycle.
Therefore the following files need a version increment:

org.eclipse.jdt.debug.tests/META-INF/MANIFEST.MF
org.eclipse.jdt.debug.tests/pom.xml

An additional commit containing all the necessary changes was pushed to the top of this PR's branch. To obtain these changes (for example if you want to push more changes) either fetch from your fork or apply the git patch.

Git patch

From 6409f8203d15eb1458642bfe1cec071bcfc7274a Mon Sep 17 00:00:00 2001
From: Eclipse JDT Bot <jdt-bot@eclipse.org>
Date: Wed, 5 Mar 2025 07:42:23 +0000
Subject: [PATCH] Version bump(s) for 4.36 stream


diff --git a/org.eclipse.jdt.debug.tests/META-INF/MANIFEST.MF b/org.eclipse.jdt.debug.tests/META-INF/MANIFEST.MF
index 3209a2c62..0fd3030ca 100644
--- a/org.eclipse.jdt.debug.tests/META-INF/MANIFEST.MF
+++ b/org.eclipse.jdt.debug.tests/META-INF/MANIFEST.MF
@@ -2,7 +2,7 @@ Manifest-Version: 1.0
 Bundle-ManifestVersion: 2
 Bundle-Name: %pluginName
 Bundle-SymbolicName: org.eclipse.jdt.debug.tests; singleton:=true
-Bundle-Version: 3.12.600.qualifier
+Bundle-Version: 3.12.700.qualifier
 Bundle-ClassPath: javadebugtests.jar
 Bundle-Activator: org.eclipse.jdt.debug.testplugin.JavaTestPlugin
 Bundle-Vendor: %providerName
diff --git a/org.eclipse.jdt.debug.tests/pom.xml b/org.eclipse.jdt.debug.tests/pom.xml
index 8c423e4b8..e7d8cab78 100644
--- a/org.eclipse.jdt.debug.tests/pom.xml
+++ b/org.eclipse.jdt.debug.tests/pom.xml
@@ -18,7 +18,7 @@
   </parent>
   <groupId>org.eclipse.jdt</groupId>
   <artifactId>org.eclipse.jdt.debug.tests</artifactId>
-  <version>3.12.600-SNAPSHOT</version>
+  <version>3.12.700-SNAPSHOT</version>
   <packaging>eclipse-test-plugin</packaging>
   <properties>
     <testSuite>${project.artifactId}</testSuite>
-- 
2.48.1

Further information are available in Common Build Issues - Missing version increments.

[SougandhS]

hi @iloveeclipse , Made all the changes suggested

[iloveeclipse]

I had some comments and changes, I will push them now.

[iloveeclipse]

@SougandhS : please provide N&N entry.

[SougandhS]

Thank you @iloveeclipse :)

@SougandhS : please provide N&N entry.

Will provide N & N 👍