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

Move from own memory view to DAP and vscode #320

Open
GitMensch opened this issue Mar 4, 2022 · 0 comments
Open

Move from own memory view to DAP and vscode #320

GitMensch opened this issue Mar 4, 2022 · 0 comments
Milestone

Comments

@GitMensch
Copy link
Collaborator

GitMensch commented Mar 4, 2022

#64 added this the best way possible back than - completely on its own.
The DAP got the Disassemble Request a while ago, so it may be possible / useful to move to this.
I haven't checked in detail but I think it would be possible to implement the dap part (increasing "only" that dependency) and depending on the version of vscode, which seems to have its frontend usable since January 2022, report "we support it".
This should give users of current vscode a nice debugging experience, even on Win32, and we can consider some versions later to remove the native-debug command, window and code altogether when increasing the vscode dependency to 2022 (which should be postponed some months).

Opinions?

@GitMensch GitMensch added this to the Backlog milestone Apr 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant