[release/8.0-staging] [debugger] Support step into a tail call #110440
Conversation
This file contains 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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Addressing Tom's and Mikelle's comments Removing unrelated change and adding enum Changing the comment.
|
Tagging subscribers to this area: @tommcdon |
tommcdon
approved these changes
Dec 5, 2024
tommcdon
approved these changes
Dec 5, 2024
jeffschwMSFT
approved these changes
Dec 5, 2024
This was referenced Dec 5, 2024
|
Approved by email. |
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.
Backport of #110334 to release/8.0-staging
/cc @thaystg
Customer Impact
#110441
A customer ships a compiler that uses tail calls and when their customers are debugging the app generated by this compiler and try to step into a tail call it behaves like a resume.
Regression
It works before .NET 6.
Testing
We manually tested using this internal test https://github.com/dotnet/runtime/blob/e99557baffbe864d624cc1c95c9cbf2eefae684f/src/tests/JIT/Regression/JitBlue/Runtime_39581/Runtime_39581.il and trying to step into the Callee.
Risk
Low risk, this will only affect the scenarios where we emit a tail call using the StoreTailCallArgs, which is not used a lot. As far as I understood it's impossible to generate it from a C# code, only F# and IL.