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: | Strange debugging steps | ||
|---|---|---|---|
| Product: | debugger | Reporter: | jojjeb <jojjeb> |
| Component: | Code | Assignee: | issues@debugger <issues> |
| Status: | CLOSED DUPLICATE | ||
| Severity: | blocker | ||
| Priority: | P3 | ||
| Version: | 6.x | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Issue Type: | DEFECT | Exception Reporter: | |
Seems like a duplicate of issue 168365. *** This issue has been marked as a duplicate of 168365 *** verified duplicate |
Strange debugging behavour: ------------------------code like------------- public boolean isInputFieldsOk( Vector<String> in ) { boolean res = true; String notAllowed = new String("00:00"); for(String str : in) { if( str.equalsIgnoreCase(notAllowed) == true) { res = false; break; } } return res; } ------------------------ When running above code in debug and break points set on line : for(String str : in) and break; Evan though the comparission is false, the debugger jumps to the break; statement within the if statement. /j