[Lldb-commits] [lldb] 7d2dce0 - [LLDB] Add always-on logging for "settings set" (#201185)

[via lldb-commits]

Author: Adrian Prantl
Date: 2026-06-02T12:49:49-07:00
New Revision: 7d2dce084307356948a3ef78c902fd68558afe2e

URL: https://github.com/llvm/llvm-project/commit/7d2dce084307356948a3ef78c902fd68558afe2e
DIFF: https://github.com/llvm/llvm-project/commit/7d2dce084307356948a3ef78c902fd68558afe2e.diff

LOG: [LLDB] Add always-on logging for "settings set"  (#201185)

When triaging bugreports it can be very useful to understand what LLDB
defaults have been changed. Adding settings to the always-on logging
channel helps with that.

rdar://176482205

Assisted-by: claude

Added: 
    

Modified: 
    lldb/source/Commands/CommandObjectSettings.cpp

Removed: 
    


################################################################################
diff  --git a/lldb/source/Commands/CommandObjectSettings.cpp b/lldb/source/Commands/CommandObjectSettings.cpp
index b09c65982a277..2c854cb05ce12 100644
--- a/lldb/source/Commands/CommandObjectSettings.cpp
+++ b/lldb/source/Commands/CommandObjectSettings.cpp
@@ -10,6 +10,7 @@
 
 #include "llvm/ADT/StringRef.h"
 
+#include "lldb/Host/Host.h"
 #include "lldb/Host/OptionParser.h"
 #include "lldb/Interpreter/CommandCompletions.h"
 #include "lldb/Interpreter/CommandInterpreter.h"
@@ -192,6 +193,8 @@ insert-before or insert-after.");
       return;
     }
 
+    LLDB_LOG(GetLog(SystemLog::System), "settings set {0}", command);
+
     // A missing value corresponds to clearing the setting when "force" is
     // specified.
     if (argc == 1 && m_options.m_force) {