https://github.com/jimingham created https://github.com/llvm/llvm-project/pull/196178
It is natural to try: ``` log enable -f file1 lldb step log enable -f file2 lldb process ``` or whatever, and then be surprised that all the logs end up in `file2`... The help on `log enable`'s `-f` option didn't specify what you were setting the file for. This PR just changes the help text to be clear about the current state of things. >From 34a2e29237931dc23fcfad035bda32700ff49867 Mon Sep 17 00:00:00 2001 From: Jim Ingham <[email protected]> Date: Wed, 6 May 2026 13:48:30 -0700 Subject: [PATCH] Make it clear that log enable's output file is per channel not per category. --- lldb/source/Commands/Options.td | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/lldb/source/Commands/Options.td b/lldb/source/Commands/Options.td index 12e06d4f8b2ad..ba6781dcab04e 100644 --- a/lldb/source/Commands/Options.td +++ b/lldb/source/Commands/Options.td @@ -867,7 +867,8 @@ let Command = "log enable" in { def log_file : Option<"file", "f">, Group<1>, Arg<"Filename">, - Desc<"Set the destination file to log to.">; + Desc<"Set the destination file that all the enabled " + "categories in the specified log channel will log to.">; def log_handler : Option<"log-handler", "h">, Group<1>, EnumArg<"LogHandler">, _______________________________________________ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
