Skip to content
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

Debug Protocol: Support step-into-specifc #39

Closed
jacdavis opened this issue Jun 24, 2016 · 3 comments
Closed

Debug Protocol: Support step-into-specifc #39

jacdavis opened this issue Jun 24, 2016 · 3 comments
Assignees

Comments

@jacdavis
Copy link

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:
stepintospecific

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.

@weinand
Copy link
Contributor

weinand commented Jun 24, 2016

@jacdavis sounds similar to #28, correct?

@weinand weinand self-assigned this Jun 24, 2016
@gregg-miskelly
Copy link
Member

@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
Copy link
Contributor

weinand commented 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
Projects
None yet
Development

No branches or pull requests

3 participants