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 31781 - Debugger Variable Validation
Summary: Debugger Variable Validation
Status: CLOSED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: issues@debugger
URL:
Keywords: ARCH
Depends on:
Blocks:
 
Reported: 2003-03-07 14:44 UTC by kyleyj
Modified: 2010-04-29 09:12 UTC (History)
2 users (show)

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 kyleyj 2003-03-07 14:44:35 UTC 
While developing a debugger for my proprietary language, 
I've noticed a that with the Debugger framework there is a 
problem with the variable validation.  As variables are 
created they are added to the validator for that debugging 
session.  However, variables are never removed from the 
validator when calling into another call stack scope or 
when leaving the call stack scope.  This leaves overhead 
that continously grows throughout a degugging session.  
Each time you call into another call stack scope, all of 
the old variables will be validated for the scope ( valid 
or not ) and then when leaving that call stack scope, all 
of the newly added variables are added to the validation 
that occurs for each line of code.
Comment 1 Jan Jancura 2003-03-10 13:26:37 UTC 
There should be weak reverence from Validator to variable. But me be
there is some problem. I will look at it soon, but I can not promise
that it will be fixed to nb3.5.
Comment 2 Maros Sandor 2003-08-19 10:03:01 UTC 
The problem is that local variables are not removed from 
the validator immediately after they go out of scope. They 
should, however, be removed by the garbage collector 
later. In any case, I consulted the it with Jan and we 
agreed that this issue does not affect rainier because 1) 
it only affects java local variables 2) watches are 
removed from the validator after they are deleted from the 
watches view. Also, examining the rainier runtime behavior 
leads me to conclusion that it does not call validate() 
method of the Validator anyway. I'm removing the rainier 
keyword.
Comment 3 Maros Sandor 2003-12-19 11:40:09 UTC 
The weak mapping does not seem to work properly, we need to rewrite 
the validating engine for the new debugger => promoD.
Comment 4 Jan Jancura 2004-05-18 09:43:46 UTC 
fixed in the main trunk.
Validation of variables has been rewritten completely.
Comment 5 Quality Engineering 2010-04-29 09:12:40 UTC 
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.