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 269276 - "OrgNetBeansDebuggerInvocationInnerClass1" is not a known variable in the current context
Summary: "OrgNetBeansDebuggerInvocationInnerClass1" is not a known variable in the cur...
Status: NEW
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 8.2
Hardware: PC Other
: P3 normal (vote)
Assignee: Martin Entlicher
Depends on:
Reported: 2016-12-09 00:20 UTC by _ gtzabari
Modified: 2017-01-10 22:26 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description _ gtzabari 2016-12-09 00:20:06 UTC
Product Version: NetBeans IDE 8.2 (Build 201609300101)
Java: 1.8.0_112; Java HotSpot(TM) 64-Bit Server VM 25.112-b15
Runtime: Java(TM) SE Runtime Environment 1.8.0_112-b15
System: Windows 10 version 10.0 running on amd64; Cp1252; en_US (nb)
User directory: C:\Users\a-gtzabari\AppData\Roaming\NetBeans\8.2
Cache directory: C:\Users\a-gtzabari\AppData\Local\NetBeans\Cache\8.2

I added a watch for "componentDao.listByMetric(existingMetric.get().getId()).stream().map(value -> value.key).collect(Collectors.toList())" and got:

"OrgNetBeansDebuggerInvocationInnerClass1" is not a known variable in the current context

I don't have such a variable/type in my application, so I can only assume this is some internal class defined by the debugger which is missing. This bug could be related to bug #51387 which re-enabled evaluation of not-yet-loaded-classes (because, off the top of my head, this defines new classes on the fly using bytecode injection). Maybe there is some sort of bug in that logic.

I don't know how to reproduce this issue. I have only seen it once so far.
Comment 1 _ gtzabari 2016-12-09 00:21:32 UTC
This bug is triggered by "map(value -> value.key)" in the expression. If I evaluate the string before this map, the result comes back okay.
Comment 2 _ gtzabari 2017-01-10 22:26:44 UTC
Another (related?) error I get is: ">Invalid path argument: className <" where className is the current class in the editor. The watch expressoin is: ""

Any idea where all these errors are coming from? They are making it impossible to debug lambda expressions.