[all-commits] [llvm/llvm-project] 41ef9d: [lldb] Add option to log in JSONL format (#205758)
Raphael Isemann via All-commits
all-commits at lists.llvm.org
Mon Jun 29 01:49:51 PDT 2026
Branch: refs/heads/main
Home: https://github.com/llvm/llvm-project
Commit: 41ef9d77f7826ec45e83ab4c6b83a96d735830c6
https://github.com/llvm/llvm-project/commit/41ef9d77f7826ec45e83ab4c6b83a96d735830c6
Author: Raphael Isemann <rise at apple.com>
Date: 2026-06-29 (Mon, 29 Jun 2026)
Changed paths:
M lldb/include/lldb/Utility/Log.h
M lldb/source/Commands/CommandObjectLog.cpp
M lldb/source/Commands/Options.td
M lldb/source/Utility/Log.cpp
M lldb/test/API/commands/log/basic/TestLogging.py
M lldb/unittests/Utility/LogTest.cpp
Log Message:
-----------
[lldb] Add option to log in JSONL format (#205758)
This patch adds a -j option to the log command that prints all log
messages as their own single-line JSON objects. The resulting output log
file is then a valid JSONL file with the message and metadata as their
own fields.
The motivation for this change is that writing any tooling that
analyzses LLDB logs is currently very difficult to get right. Our
current log messages often span multiple lines, and even the metadata
(e.g., stacktraces) span multiple lines. Even worse, the message content
is effectively arbitrary bytes (such as memory values) that need can
only be parsed back into a series of log messages via several
heuristics.
assisted-by: claude
To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications
More information about the All-commits
mailing list