Community
Participate
Working Groups
Java debugger fails to evaluate expression in context of method with generic typed argument. Following error is reported "The method ... in type ... is not applicable for arguments (...)" Steps to reproduce --- Below is snippet of code reproducing a problem. public class EclipseDebugIssue<T> { private void methodA(SomeClass<T> obj) { methodB(obj); } private int methodB(SomeClass<T> obj) { return 42; } public static void main(String[] args) { EclipseDebugIssue<String> t = new EclipseDebugIssue<String>(); t.methodA(new SomeClass<String>("A")); } } class SomeClass<T> { private T val; public SomeClass(T val) { this.val = val; } } Put breakpoint in method "methodA" At break point try to inspect expression "methodB(obj" Following error would be shown "The method methodB(SomeClass<T>) in type EclipseDebugIssue<T> is not applicable for arguments (SomeClass<T>)"
Can reproduce the bug, will look into this in M3.
Not able to find time in M3
Which Java version is set for the workspace compiler settings? If it is <1.5 then please set the compliance to higher version - will it fix the issue? We had similar problems in a 1.8 project where the debugger resolved Java compliance not from the project itself but from "external dependencies" hidden project, which in turn uses compiler settings from the workspace.
Moving it out of 4.8.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
Bug is still not fixed.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
