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.

Bug 59070 - Conditional breakpoints stop on invalid conditions
Summary: Conditional breakpoints stop on invalid conditions
Status: CLOSED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 5.x
Hardware: PC All
: P3 blocker (vote)
Assignee: issues@debugger
URL:
Keywords: USABILITY
Depends on:
Blocks:
 
Reported: 2005-05-19 16:18 UTC by Martin Entlicher
Modified: 2010-04-29 09:22 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Entlicher 2005-05-19 16:18:57 UTC 
1) When an invalid condition is provided, the user is not warned.
2) When the condition is not possible to evaluate, the user is not warned again
and the debugger stops there.
Comment 1 _ lcincura 2005-05-24 13:55:10 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.
Comment 2 Martin Entlicher 2005-05-24 22:36:41 UTC 
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.
Comment 3 Martin Entlicher 2005-10-04 16:57:05 UTC 
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
Comment 4 Quality Engineering 2010-04-29 09:22:42 UTC 
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.