This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
| Summary: | Debug steps are sometimes misleading | ||
|---|---|---|---|
| Product: | debugger | Reporter: | shadewind <shadewind> |
| Component: | Java | Assignee: | issues@debugger <issues> |
| Status: | CLOSED WONTFIX | ||
| Severity: | blocker | ||
| Priority: | P3 | ||
| Version: | 6.x | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Issue Type: | DEFECT | Exception Reporter: | |
I've reproduced the behavior. But this can not be fixed in NetBeans. The locations where debugger stops are generated by compiler. I've submitted a defect for javac compiler - 6765597. Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier. |
for(ServiceInfo serviceInfo : services.values()) { if(type.isAssignableFrom(serviceInfo.getType()) && serviceInfo.hasServiceKey(key)) return serviceInfo; } Consider debugging code snippet like the above example. When looping through it, even if the if-clause holds false, the step cursor will "step on" the "return serviceInfo;" line anyway. This is confusing as it leads me to believe that the if-clause actually held true when it didn't. The step cursor should land on the closing brace '}' instead if the if-clause is skipped which would be a lot clearer.