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.

Sign up for GitHub

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

Jump to bottom

"Skip path" configuration makes VSCode stop at breakpoint, but not jump to definition #849

Closed
marianosimone opened this issue Nov 30, 2022 · 1 comment · Fixed by #850
Closed

"Skip path" configuration makes VSCode stop at breakpoint, but not jump to definition #849

marianosimone opened this issue Nov 30, 2022 · 1 comment · Fixed by #850

Comments

@marianosimone
Copy link
Contributor

marianosimone commented Nov 30, 2022 •
edited
Loading

To Reproduce

  • Set a breakpoint
  • Configure skip_path to include the path of the breakpoint
  • Debug in VSCode

Expected behavior
The breakpoint should be respected, and VSCode should jump to the definition of where the issue is

Actual behavior
The debugger stops, but VSCode can't jump to the definition, because the path is skipped (starting in [debug/pr/749] 🐛 Respect skip_path when returning the backtrace in ServerDAP)
@marianosimone marianosimone mentioned this issue Nov 30, 2022
Merged
@ko1
Copy link
Collaborator

ko1 commented Nov 30, 2022

Wow...

@ko1 ko1 closed this as completed in #850 Nov 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

🐛 Respect breakpoints even when in a skipped path
2 participants
@ko1 @marianosimone