search

lldb-tools / lldb-mi

LLDB's machine interface driver
https://lldb.llvm.org
Other
165 stars 56 forks source link

Temporary fix for memory leak when reading variables #115

Closed sunshaoce closed 10 months ago

sunshaoce commented 11 months ago

This is a temporary solution, from @shiretu https://github.com/microsoft/vscode-cpptools/issues/7240#issuecomment-997954449 . I'm not sure if it really works, so I hope everyone can give more feedback, thank you!

Related issues: https://github.com/microsoft/vscode-cpptools/issues/1899 https://github.com/microsoft/vscode-cpptools/issues/5805 https://github.com/microsoft/vscode-cpptools/issues/7240 https://github.com/microsoft/vscode-cpptools/issues/9488 https://github.com/microsoft/vscode-cpptools/issues/9831 https://github.com/llvm/llvm-project/issues/53634 https://github.com/lldb-tools/lldb-mi/issues/89 https://github.com/lldb-tools/lldb-mi/issues/101 https://github.com/vadimcn/codelldb/issues/987 https://github.com/vadimcn/codelldb/issues/998

Co-authored-by: Eugen-Andrei Gavriloaie andrei@gavriloaie.com

sunshaoce commented 10 months ago

It looks like no one has any objections to this PR.

sunshaoce commented 3 months ago

@clayborg Thanks for your comments. Would you like to make a PR to fix this, considering there are fewer people developing this project?

clayborg commented 2 months ago

I don't work with the MI layer anymore.

If this is being used in Visual Studio Code, the LLDB project fully supports a native lldb-dap plug-in that interfaces directly with the IDE without going through the GDB MI layering. I would suggest switching cppdebug over to using this as we actively maintain this.