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 12729 - Debugger does not catch String values
Summary: Debugger does not catch String values
Status: CLOSED DUPLICATE of bug 7504
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P2 blocker (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on: 7504
Blocks:
  Show dependency tree
 
Reported: 2001-06-10 08:57 UTC by emmanuel
Modified: 2001-07-20 20:35 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 emmanuel 2001-06-10 08:57:39 UTC 
The debugger does not catch processing when a String variable reaches a certain 
value?  The help says this is possible, but every iteration stops at the 
breakpoint, not only when the condition evaluates true.

The particular condition is used is, entry.equals("Html").
BTW, I also used entry=="Html".

Note, conditional breakpoints of int variables are caught.

Can this be corrected please.
Comment 1 Daniel Prusa 2001-06-11 09:31:13 UTC 
This problem is related to issue 7054 - expression evaluator does not work 
well. As for the described situation:
1) Methods cannot be invoked on instances of String, thus equals does not work.
2) Comparison between an instance of String and a String literal always results 
as false.

Implementation of a new (reliable) evaluator is "Must have feature" for 
NetBeans 3.3 release.
Comment 2 emmanuel 2001-06-11 10:00:47 UTC 
Daniel, thank you for your feedback.  Does this mean that once issue 7504 
(planned "improved expression evaluator") is implemented that String evaluation 
in debugging would be catered for?
Comment 3 Daniel Prusa 2001-06-11 10:38:07 UTC 
Yes, once we implement "improved expression evaluator" String evaluation will 
be fixed.
Comment 4 emmanuel 2001-06-11 19:12:31 UTC 
Danie, thank you for your feedback.  This is great news.
Looking forward to the improved release.
Regards, Emmanuel
Comment 5 Jan Stola 2001-06-15 14:51:14 UTC 

*** This issue has been marked as a duplicate of 7054 ***
Comment 6 Jan Stola 2001-06-15 14:52:38 UTC 
.
Comment 7 Jan Stola 2001-06-15 14:56:07 UTC 
This bug was resolved as a duplicate of issue 7054 by accident.
I took this number from the comment of Daniel Prusa,
but this was a worng number. It should be marked as duplicate
of issue 7504.

*** This issue has been marked as a duplicate of 7504 ***