Repository navigation
lambda expression doesn't apply to the right java file. #41
Description
Step: use debugger to debug itself, step in computeIfAbsent in StackTraceRequestHandler.java@112
{{ message }}
Step: use debugger to debug itself, step in computeIfAbsent in StackTraceRequestHandler.java@112
Activity
andxu commentedon Sep 21, 2017
The first stacktrace has the wrong java file name
andxu commentedon Sep 21, 2017
By the way, I cannot step over inside lambda express:
String uri = context.getSourceLookupCache().computeIfAbsent(fullyQualifiedName, key ->
context.getProvider(ISourceLookUpProvider.class).getSourceFileURI(key, finalRelativeSourcePath)
);
andxu commentedon Sep 21, 2017
Another issue is a lot of unknown sources in stack frame during debug idea, which has only method names which is very confusing.
testforstephen commentedon Oct 13, 2017
The lambda expression issue has been resolved. As to the improvement of method names in call stack view is duplicated with #43