Community
Participate
Working Groups
public class SaveBreakPoint { public static void main(final String[] args) { for (int i = 0; i < 10; i++) { // Conditional BreakPoint on next line for i == 5 System.out.println(i); } } } Steps to reproduce: 1. Set conditional breakpoint on the sysout for i == 5 2. Launch a debug run and confirm the breakpoint is working as expected 3. Modify the condition in the breakpointsview in the details panel to i == 3 4. Observe a * in the tab title for the dirty status 5. Launch another debug run by clicking the bug-icon in the main toolbar 6. The * is removed, but the program ran till i == 5 and stopped there. Expected: Save dirty breakpoints before launching the debug session.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
Still happens in Version: 2020-09 (4.17) Build id: I20200902-1800 java.version=15.0.1 java.version.date=2020-10-20 java.vm.name=OpenJDK 64-Bit Server VM
Will try to look at this in 4.19.
Investigated the problem. The save is not being called by the launch but it is accidentally called by the UI Part rendering system. Same issue with Bug 573604 ! It is not straight forward to access the breakpoint view at the launch time to be able to save the edit conditional editor. Will not be able to work on this further, if some one can provide a patch, will look into it.
