[all-commits] [llvm/llvm-project] 9b096b: [lldb] Add SBProtocolServer to start protocol serv...

[Jonas Devlieghere via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 9b096bb7abf7b57182ae8556451aa34dacd535ec
      https://github.com/llvm/llvm-project/commit/9b096bb7abf7b57182ae8556451aa34dacd535ec
  Author: Jonas Devlieghere <jonas at devlieghere.com>
  Date:   2026-07-17 (Fri, 17 Jul 2026)

  Changed paths:
    M lldb/bindings/interfaces.swig
    M lldb/include/lldb/API/LLDB.h
    M lldb/include/lldb/API/SBDefines.h
    A lldb/include/lldb/API/SBProtocolServer.h
    M lldb/source/API/CMakeLists.txt
    A lldb/source/API/SBProtocolServer.cpp
    M lldb/unittests/API/CMakeLists.txt
    A lldb/unittests/API/SBProtocolServerTest.cpp

  Log Message:
  -----------
  [lldb] Add SBProtocolServer to start protocol servers programmatically (#209923)

Starting a protocol server (such as MCP, and in the future potentially
DAP) is only possible from the command line today, via `protocol-server
start`. Add an SB API so an embedder can start one in its own process
and learn where to connect.

SBProtocolServer wraps ProtocolServer::GetOrCreate/Start/Stop and
exposes the listening connection URI. This lets a tool host the engine's
protocol server in-process and talk to it as a normal client, reusing
the server's tools rather than reimplementing them.

Assisted-by: Claude



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