-
Notifications
You must be signed in to change notification settings - Fork 117
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
Examine-memory debugger selections not removed on uninstall #378
Comments
What do you mean by "new entry to the debugger list"? Side question: do you know if there is an activation of extensions "onUninstall" / "onDisable"? I'm not sure that it is; and then there would be no option to remove something there (can obviously only be done when the extension is triggered). |
The debugger prompt that is displayed when you run Code-Debug: Examine
memory location:
[image: image.png]
No idea, but from having a lot of install experience, my guess is that the
extension data is located in the wrong place where the data lifetime is
permanent. E.g., instead of being located in a per-VS-session location,
it's being stored in a permanently-scoped location, so it is left on
purpose by design.
A quick workaround would be add a command to clear the debuggers list or
delete entries from it. Really not what's needed but hey that would help
right now!
…On Fri, Sep 23, 2022 at 2:19 PM Simon Sobisch ***@***.***> wrote:
What do you mean by "new entry to the debugger list"?
Side question: do you know if there is an activation of extensions
"onUninstall" / "onDisable"? I'm not sure that it is; and then there would
be no option to remove something there (can obviously only be done when the
extension is triggered).
—
Reply to this email directly, view it on GitHub
<#378 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFCPGNT3HZSB6Q3JKSS33EDV7XYEHANCNFSM6AAAAAAQUDQVPA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Images can only be posted vie GitHub online, not by mail, please post that again. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sometime when I invoke the Code: Examine Memory window (which is wonderful to have), it adds a new entry to the debugger list that is never removed. Even uninstalling and reinstalling the extension twice does not remove these entries. I'm not sure what causes them to be abandoned.
The bug is that when the extension is uninstalled, these abandoned entries should definitely be removed.
Remote: PhotonOS, gdb RHEL 7.6.1-120.el7. Latest extension code as of 2022 Sept 23, 4/16/2022, 02:03:38 release.
NOTES:
The text was updated successfully, but these errors were encountered: