-
Notifications
You must be signed in to change notification settings - Fork 82
Debug Protocol: Support step-into-specifc #39
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
Labels
Comments
@weinand not really. Set next statement alters the instruction pointer in an artificial way. Step-into-specific is a special kind of step request which does a combination of step-over and step-into to only step-into one specific call site. |
weinand
added a commit
that referenced
this issue
Jul 14, 2016
@gregg-miskelly @jacdavis @DavidKarlas I've created a proposal for this protocol addition as PR 44. Please review and comment. |
weinand
added a commit
that referenced
this issue
Jul 19, 2016
Proposed protocol addition "step-into-specifc" #39
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In order to use the vscode protocol in vs and xamerin, we'd need to support Step-into-specific. This is a feature that allows the user to select which call a step in should occur on when there are multiple calls on a line. Users primarily use this when there are a lot of calls on a single line (either implicit or otherwise).
This is a trivial example:

The apis around this would require the debug adapter to provide a list of calls at a specific line. The user would then select one. The target call would then be placed as an optional field in the step-in request.
The text was updated successfully, but these errors were encountered: