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 137424 - is not a known variable in current context
Summary: is not a known variable in current context
Status: CLOSED INVALID
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All Windows Vista
: P1 blocker (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-17 13:11 UTC by puce
Modified: 2010-04-29 09:40 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description puce 2008-06-17 13:11:38 UTC
There are many situation where a local variable doesn't get displayed in the "Local Variables" window. This seems to be
(sometimes ?) the case when local variables hide fields.
I also faced this problem when I debugged eg. into javax.swing.JTable, even if local variables don't hide fields.

In all these cases, when I add the variable to the watches or display the value in the tooltip of the editor I get:
>"<varname>" is not a known variable in current context<

This is really a big problem!
Comment 1 Martin Entlicher 2008-06-17 14:02:08 UTC
I do not see any problems when evaluating local variables, which hide fields. Can you please describe the exact case
that does not work for you?

In case of javax.swing.JTable it's normal that you do not see local variables at all. JDK classes are not compiled with
debug information, therefore debugger has no way to recognize them.
Comment 2 puce 2008-06-17 15:17:25 UTC
Hmm, last time I faced this problem was in the JTable I think (I haven't found any documentation about how removing the
last row in a table model affects the lead selection index, neither in the API docs nor in Sun's Java tutorial. It seems
not to be set < 0. I tried to debug that but couldn't get the necessary debug information, which seemed very odd in that
moment.) I know it happend at other, not JTable related places, where local variables hid fields. But I can't remember
if those were in JDK classes, too. Sorry for that. I will keep an eye on this. It's ok with me if we leave this issue as
RESOLVED INVALID and reopen it if I see this problem in my own classes.
Comment 3 Quality Engineering 2010-04-29 09:40:25 UTC
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.