-
Couldn't load subscription status.
- Fork 5.2k
[release/9.0-staging] [debugger] Support step into a tail call #110438
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
[release/9.0-staging] [debugger] Support step into a tail call #110438
Conversation
|
Tagging subscribers to this area: @tommcdon |
Addressing Tom's and Mikelle's comments Removing unrelated change and adding enum Changing the comment.
306002e to
cf2be04
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm. we will take for consideration in 9.0.x
|
Approved by email. |
|
/ba-g Build analysis blocked by #110517 |
Backport of #110334 to release/9.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.