Community
Participate
Working Groups
Build Identifier: Eclipse 3.6 M6 I20100312-1448 When you set a condition for a breakpoint, it does not get saved until you change the focus from out of the box. This may lead to confusion, as a breakpoint will appear to be conditional in the breakpoint view and on the editor marker, but it will just act as a normal breakpoint. Reproducible: Always Steps to Reproduce: 1. Set 2 breakpoints in a simple java program 2. Start a debug session 3. Set a false condition for the last breakpoint (ie. 1==2) and leave focus in the text area 4. Press run 5. Notice breakpoint is hit when it should not be
This is working as designed. If you edit a condition you can save it using CTRL-S, or the save action in the file menu or toolbar (note the view shows it is dirty). Else, we auto save when you change focus, so the user does not lose work.
> we auto save when you change focus That would be fine, but that's not what I see with I20100527-1700: - When I edit the condition and then give focus to another view or to an editor, the Breakpoints view stays dirty. Expected: Should auto-save, like when I click another UI element in the Breakpoints view - When I edit the condition and then click the Debug button in the main toolbar, the condition eventually gets saved, but not before the target is launched, so it sometimes still uses the old condition when the breakpoint is hit the first time. To see that, set a breakpoint at the start of a main method, set condition to System.out.println("a"); return false; , change "a" to "b", and then click Debug.
Just wasted a whole bunch of time with this. The only feedback that your changes to your breakpoint condition have not been saved is the little asterisk by the tab title, which I didn't notice. Especially confusing since any other changes in that view are saved immediately.
Created attachment 183432 [details] patch The same editing/saving issue exists with breakpoint hit counts. This is a work in progress. It still needs some polish.
Created attachment 183488 [details] patch Applies a 200ms delay befores saving changes. Hit count is not working properly yet.
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.
