[Lldb-commits] [lldb] Add commands to list/enable/disable plugins (PR #134418)

Greg Clayton via lldb-commits lldb-commits at lists.llvm.org
Mon Apr 7 11:02:19 PDT 2025


clayborg wrote:

> Either no one is going to use this except experts, or people will start cargo-culting "turn off plugin X and lldb will be faster" and then we get "Why doesn't 'obvious thing'" work bug reports, to which the answer would be "turn on plugin X" but people may not even know they have this off (a surprising number of folks don't really know what's in the .lldbinit they got from their helpful colleagues...) I don't want to have to have another round of information gathering every time we get a report of some weird behavior.
> 
> So we should make sure that any way that we have of gathering report information includes which plugins are disabled. For instance, if you turn on any log channel, there should be a crunchy frog notice at the beginning of the log for what plugins have been disabled.
> 
> Another way to do this would be to have the list of disabled plugins show in the result of the `version` command, since that's a commonly provided bit of info for bug reports.

Can we include the plug-in info in the "statistics dump" output? We could easily JSON'ify the enabled/disabled status of all plug-ins there? Let us know if that would be acceptable

https://github.com/llvm/llvm-project/pull/134418


More information about the lldb-commits mailing list