Bugzilla – Full Text Bug Listing
| Summary: | Debugger steps into conditional breakpoint | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Andre Doerscheln <ad> |
| Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> |
| Status: | ASSIGNED --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | ad, sarika.sinha |
| Version: | 4.6 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows NT | ||
| Whiteboard: | stalebug | ||
I am not bale to reproduce this problem. I tested it on multiple systems running Windows and Eclipse 4.6. The same thing happens on all of them. IMPORTANT: I forgot to say, that it happens only if you use "step into" (F5), when debugger hits the breakpoint. (In reply to Andre Doerscheln from comment #2) > I tested it on multiple systems running Windows and Eclipse 4.6. The same > thing happens on all of them. > > IMPORTANT: I forgot to say, that it happens only if you use "step into" > (F5), when debugger hits the breakpoint. Thanks, Now I can reproduce it with "Step Into" 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. 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. |
When hitting a conditional breakpoint that is positioned at the head of a loop and that contains function-calls, the debugger will step into the conditions code and hang there. Example Code: public class DebugTest { public static void main(String[] args) { int i = 0; while (i++ < 1) { } } public static boolean test() { return true; } } Set the conditional breakpoint to line 4 (the while-loop) and the condition to: test()