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

Support Dynamic Child / Thread Selection #67

Open
colin-grant-work opened this issue Feb 13, 2024 · 0 comments · May be fixed by #133
Open

Support Dynamic Child / Thread Selection #67

colin-grant-work opened this issue Feb 13, 2024 · 0 comments · May be fixed by #133

Comments

@colin-grant-work
Copy link
Contributor

Description

Would close eclipse-cdt-cloud/cdt-gdb-vscode#110.

The goal here is to support the multi-child use cases currently supported by the cdt-gdb-vscode plugin so that the memory browser functionality in that plugin could be replaced with the Memory Inspector and future development efforts could focused here.

Cf. this comment

Additional information
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
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add Debug Context Selector WyoTwT/vscode-memory-inspector
1 participant
@colin-grant-work