-
Notifications
You must be signed in to change notification settings - Fork 12
Issues: eclipse-cdt-cloud/vscode-memory-inspector
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Running the memoryinspector in WSL
bug
Something isn't working
#150
opened Oct 31, 2024 by
jlonnberg
Form validated before initial values loaded
bug
Something isn't working
#145
opened Sep 20, 2024 by
colin-grant-work
Transient preferences lost when view popped out
bug
Something isn't working
#141
opened Jun 28, 2024 by
colin-grant-work
Improve subgroup for settings from "Memory-inspector" to "Memory Inspector"
#119
opened Mar 26, 2024 by
martin-fleck-at
Support different memory address representations for variables
#107
opened Mar 13, 2024 by
martin-fleck-at
Allow to set data breakpoints in memory view via context menu
enhancement
New feature or request
#102
opened Mar 12, 2024 by
planger
Transmit whole preference section rather than individual fields
#90
opened Mar 1, 2024 by
colin-grant-work
Proposal: Use React context instead of prop drilling for accessing shared state
#84
opened Feb 27, 2024 by
tortmayr
Refine Variable Tracker to make use of more hints from DAP Variable type
#68
opened Feb 17, 2024 by
jreineckearm
Worth using something other than React?
question
Further information is requested
#15
opened Feb 10, 2023 by
colin-grant-work
Implement ability to compare state of two memory widgets
enhancement
New feature or request
#9
opened Feb 10, 2023 by
colin-grant-work
Previous Next
ProTip!
What’s not been updated in a month: updated:<2024-10-30.