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: | Conditional breakpoints stop on invalid conditions | ||
---|---|---|---|
Product: | debugger | Reporter: | Martin Entlicher <mentlicher> |
Component: | Java | Assignee: | issues@debugger <issues> |
Status: | CLOSED FIXED | ||
Severity: | blocker | Keywords: | USABILITY |
Priority: | P3 | ||
Version: | 5.x | ||
Hardware: | PC | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Martin Entlicher
2005-05-19 16:18:57 UTC
This behaviour was threated as correct in test specififcation of debugger since NB3.6. Is the new behaviour in second case better from user point of view? Would be great if we can get suggestion from HIE. I consider the current behavior as confusing. When we got an error during parsing of the expression, we should tell to ther user that there is a problem. The same is true for the evaluation. The user might think that the condition was satisfied when the debugger stopped, while it can not be evaluated. This is misleading. An error notification is printed into Debugger Console if the condition can not be evaluated: /cvs/debuggerjpda/ui/src/org/netbeans/modules/debugger/jpda/ui/BreakpointOutput.java,v <-- BreakpointOutput.java new revision: 1.17; previous revision: 1.16 Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier. |