[all-commits] [llvm/llvm-project] 2ceab1: [lldb] Move Diagnostics from Utility to Core (NFC)...

[Jonas Devlieghere via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 2ceab13545c27aa73ec37666891189456d4af11e
      https://github.com/llvm/llvm-project/commit/2ceab13545c27aa73ec37666891189456d4af11e
  Author: Jonas Devlieghere <jonas at devlieghere.com>
  Date:   2026-06-26 (Fri, 26 Jun 2026)

  Changed paths:
    M lldb/include/lldb/Core/Debugger.h
    A lldb/include/lldb/Core/Diagnostics.h
    R lldb/include/lldb/Utility/Diagnostics.h
    M lldb/source/API/SBDebugger.cpp
    M lldb/source/Commands/CommandObjectDiagnostics.cpp
    M lldb/source/Core/CMakeLists.txt
    A lldb/source/Core/Diagnostics.cpp
    M lldb/source/Initialization/SystemInitializerCommon.cpp
    M lldb/source/Utility/CMakeLists.txt
    R lldb/source/Utility/Diagnostics.cpp

  Log Message:
  -----------
  [lldb] Move Diagnostics from Utility to Core (NFC) (#206152)

Nothing in the Utility or Host layers uses Diagnostics. Its only callers
are Debugger (the always-on log feeder), SBDebugger, and the
SystemInitializerCommon lifecycle. Those all live in Core or above. The
header depends only on Utility primitives (FileSpec, Log, Error), and
lldbInitialization already links lldbCore, so the move adds no new link
dependency anywhere.

Relocating it to Core lets Diagnostics reach Debugger, Target,
CommandInterpreter, and Host, which simplifies an upcoming change that
collect a richer diagnostics bundle (statistics, command snapshots,
invocation, etc) and allows us to implement that directly in the
Diagnostics class.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications