Skip CallEntryPoint in debugger single-step to prevent false stop#127156
Merged
tommcdon merged 3 commits intodotnet:mainfrom Apr 20, 2026
Merged
Skip CallEntryPoint in debugger single-step to prevent false stop#127156tommcdon merged 3 commits intodotnet:mainfrom
tommcdon merged 3 commits intodotnet:mainfrom
Conversation
When stepping next at the last line of Main, the debugger lands in the managed Environment.CallEntryPoint which stops the debuggee in a frame with no source info rather than the process simply exiting. Extend the existing IsInteropStub check in TriggerSingleStep to also recognize g_pEnvironmentCallEntryPointMethodDesc. When the single-step lands there, disable it and let the process exit naturally, matching the previous behavior when the return landed in native code. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
|
Tagging subscribers to this area: @steveisok, @tommcdon, @dotnet/dotnet-diag |
Contributor
There was a problem hiding this comment.
Pull request overview
Adjusts CoreCLR debugger stepping behavior so that stepping off the end of Main doesn’t land in System.Environment.CallEntryPoint (a runtime helper frame without source), and instead behaves like stepping into native code so the process can exit naturally.
Changes:
- Extends the “ignore interop stub single-step” special-case to also ignore
Environment.CallEntryPoint(g_pEnvironmentCallEntryPointMethodDesc) inDebuggerStepper::TriggerSingleStep. - Updates logging/commentary to reflect the expanded behavior and rationale.
steveisok
approved these changes
Apr 20, 2026
am11
approved these changes
Apr 20, 2026
Member
am11
left a comment
am11
left a comment
There was a problem hiding this comment.
Thank you! I was relying on public test infra. :)
jkotas
reviewed
Apr 20, 2026
jkotas
reviewed
Apr 20, 2026
This was referenced Apr 20, 2026
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
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.
When stepping next at the last line of Main, the debugger lands in the managed Environment.CallEntryPoint which stops the debuggee in a frame with no source info rather than the process simply exiting.
Extend the existing IsInteropStub check in TriggerSingleStep to also recognize g_pEnvironmentCallEntryPointMethodDesc. When the single-step lands there, disable it and let the process exit naturally, matching the previous behavior when the return landed in native code.
Found with internal VS debugger testing.