Debugger - broken step over and crashed when using labda #257
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
dkimitsa
commented
Jan 22, 2018
- It was not possible to step over code if this code was generating exception (even if it was handling it)
- Debugger was incorrectly resolving scope of local variables if their usage was starting with invoking of lambda
…e there is an exception thrown (even handled one) in code that being stepped over/out. E.g. it was not possible to go through following code:
new File("/some/invalid/path").exists();
new File("/some/invalid/path").exists();
as it throws/handles internal exceptions
…its first unit was set to lambda invocation code generated by RoboVM compiler. as during replacement of DynamicInvokeExpr it wasn't copied line number information
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.