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

Stepping when in a skipped frame navigates me back out to the last non skipped frame #95954

Closed
alexr00 opened this issue Apr 23, 2020 · 7 comments
Assignees
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues feature-request Request for new features or functionality help wanted Issues identified as good community contribution opportunities *out-of-scope Posted issue is not in scope of VS Code
Milestone

Comments

@alexr00
Copy link
Member

alexr00 commented Apr 23, 2020

Repro steps:
Debug something that will have skipped frames
Break in
Step into a function that will be in in a skipped frame
Keep stepping over some stuff in the skipped frame

Expected: I intentionally stepped in, I expect to go to that file
Actual: each time I step over while in a skipped frame in I'm shown the editor that the last non skipped frame was from. This means I have to keep re-opening the frame I care about.
confusingStepping

@isidorn
Copy link
Contributor

isidorn commented Apr 23, 2020

Good point and agree with your request.
I will not have time this milestone, thus assigning to On-Deck.
Here's a code pointer in case someone wants to tackle it in the meantime https://github.com/microsoft/vscode/blob/1af3b9dce3d2ead4c3c0bb010dc47a4752af13d1/src/vs/workbench/contrib/debug/browser/debugService.ts#L1144
Basically the autoFocus of frames should take into account the previous one if it is deempahisezed.

@isidorn isidorn added debug Debug viewlet, configurations, breakpoints, adapter issues feature-request Request for new features or functionality help wanted Issues identified as good community contribution opportunities labels Apr 23, 2020
@isidorn isidorn added this to the On Deck milestone Apr 23, 2020
@dongskyler
Copy link

dongskyler commented Apr 24, 2020

I'd like to tackle this issue.

@isidorn The code pointer link doesn't seems to work. Could you help me out here? Thank you.
https://github.com/microsoft/vscode/blob/1af3b9dce3d2ead4c3c0bb010dc47a4752af13d1/src/vs/workbench/contrib/debug/browser/debugService.ts#L1144

@isidorn
Copy link
Contributor

isidorn commented Apr 24, 2020

Sorry, my mistake.
Here's a correct one

stackFrame = first(callStack, sf => !!(sf && sf.source && sf.source.available && sf.source.presentationHint !== 'deemphasize'), undefined);

@dongskyler
Copy link

dongskyler commented Apr 25, 2020

@isidorn Thank you. That’s very helpful. I’m looking into the issue. My initial impression is: it seems, near Line 1144, the if (!stackFrame) section isn’t taking some corner cases into considerations. I’ll post some updates shortly.

@dongskyler
Copy link

Just to give an update. I'm still working on it. This will be my first contribution to VS Code. Sorry it is taking some time, but I am making progress.

@isidorn
Copy link
Contributor

isidorn commented Apr 30, 2020

No hurries. Take your time.

@isidorn isidorn added the *out-of-scope Posted issue is not in scope of VS Code label Nov 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues feature-request Request for new features or functionality help wanted Issues identified as good community contribution opportunities *out-of-scope Posted issue is not in scope of VS Code
Projects
None yet
Development

No branches or pull requests

4 participants
@isidorn @dongskyler @alexr00 and others