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 6878

Summary: There should be access/modification variable breakpoint.
Product: debugger Reporter: Jan Stola <jstola>
Component: JavaAssignee: Jan Jancura <jjancura>
Status: CLOSED WONTFIX    
Severity: enhancement    
Priority: P4    
Version: 3.x   
Hardware: All   
OS: All   
Issue Type: ENHANCEMENT Exception Reporter:

Description Jan Stola 2000-06-22 14:18:13 UTC 
If you want to add variable breakpoint on both access and modification,
you have to add two breakpoints. I think there should be variable
breakpoint on access/modification (like the thread breakpoint on start/stop).
Comment 1 Jan Stola 2000-07-27 17:33:59 UTC 
Bug assigned to the module owner.
Comment 2 Petr Slegr 2000-09-04 02:06:59 UTC 
I agree, that would be useful. But I think that a certain problem with
interpreting of breakpoint types' terms may occurr (even now!).

Now we have access and modification VARIABLE breakpoints. And one can understand
it that access means both reading and modifying value. However, modification of
variable's value is not possible without accessing the variable...

Do you feel the different between "access VALUE (of variable)" and "acces
VARIABLE"?

What about following new names:
1)
- read value
- write value
- r/w

2)
- use (i.e. read)
- modification (i.e. write)
- access (including both)

The first version is propably clearer.
Comment 3 Jan Jancura 2000-11-06 14:24:59 UTC 
Moved to ToDo List:
http://debuggercore.netbeans.org/docs/NewFeatures.html#There should be
access/modification variable breakpoint.
Comment 5 Jan Jancura 2001-06-19 08:33:57 UTC 
going to close
Comment 6 Jan Jancura 2001-06-19 08:52:02 UTC 
Planned for NB3.3
See http://debuggercore.netbeans.org/docs/NewFeatures33.html
Comment 7 Quality Engineering 2003-06-30 17:34:45 UTC 
Resolved for 3.3.x or earlier, no new info since then -> closing.
Comment 8 Quality Engineering 2003-06-30 17:36:15 UTC 
Resolved for 3.3.x or earlier, no new info since then -> closing.