* fixed: NumberFormatException when compiling 1.4/1.5 kotlin code for Debugger #581
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
… Debugger Root case: kotlin compiler now generate SMAP data in different format: > In KotlinDebug, they use `1#2,3:4` to mean "map lines 4..6 to line 1 of MobiVM#2", when in reality (and i > the non-debug stratum) this maps lines 4..6 to lines 1..3. The correct syntax is `1#2:4,3`. In general now three formats are possible: * case 1: "$source#$fileId:$dest\n" * case 2: "$source#$fileId:$dest,$range" * case 3: "$source#$fileId,$range:$dest" This commit adds support for all three formats
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.
Root case: kotlin compiler now generate SMAP data in different format:
In general now three formats are possible:
This PR adds support for all three formats