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

---

Additionally a new option has been added to the Java editor to toggle Triggerpoints, allowing users to
instantly create a Resume-Triggerpoint.

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]

expecting @since 3.22

00:01:32.006  [ERROR] Failed to execute goal org.eclipse.tycho:tycho-apitools-plugin:4.0.11:verify (verify) on project org.eclipse.jdt.debug: There are API errors:
00:01:32.006  [ERROR] model/org/eclipse/jdt/debug/core/IJavaBreakpoint.java:54 Invalid @since 3.5 tag on RESUME_THREAD; expecting @since 3.22

note that this change has to wait for M1 anyway and then you may need to bump one more time

[SougandhS]

Yes, will correct for next M1

[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 👍