Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lambda expression doesn't apply to the right java file. #41

Closed
andxu opened this issue Sep 21, 2017 · 4 comments
Closed

lambda expression doesn't apply to the right java file. #41

andxu opened this issue Sep 21, 2017 · 4 comments
Assignees
Milestone

Comments

@andxu
Copy link
Contributor

andxu commented Sep 21, 2017

Step: use debugger to debug itself, step in computeIfAbsent in StackTraceRequestHandler.java@112

image

@andxu
Copy link
Contributor Author

andxu commented Sep 21, 2017

image
The first stacktrace has the wrong java file name

@andxu
Copy link
Contributor Author

andxu commented 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
Copy link
Contributor Author

andxu commented 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
Copy link
Contributor

The lambda expression issue has been resolved. As to the improvement of method names in call stack view is duplicated with #43

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants