[all-commits] [llvm/llvm-project] ff65d8: [lldb] Drop client-side Python pre-load and remove...

[Jonas Devlieghere via All-commits]

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

  Changed paths:
    R lldb/include/lldb/Host/windows/PythonPathSetup/PythonPathSetup.h
    M lldb/source/Host/CMakeLists.txt
    R lldb/source/Host/windows/PythonPathSetup/CMakeLists.txt
    R lldb/source/Host/windows/PythonPathSetup/PythonPathSetup.cpp
    M lldb/tools/driver/CMakeLists.txt
    M lldb/tools/driver/Driver.cpp
    M lldb/tools/lldb-dap/tool/CMakeLists.txt
    M lldb/tools/lldb-dap/tool/lldb-dap.cpp

  Log Message:
  -----------
  [lldb] Drop client-side Python pre-load and remove PythonPathSetup (#200533)

PythonPathSetup was a Windows-only helper that pre-mapped python3xx.dll
into lldb.exe / lldb-dap.exe so liblldb.dll's direct imports from
python3xx.dll would resolve when the delay-load thunk for liblldb fired
on the first SB call. ScriptInterpreterRuntimeLoader's Windows backend
has subsumed that responsibility, so this commit deletes the helper and
rewrites the two clients on the new API.

The Windows pre-load itself stays in the clients: the central load in
SystemInitializerFull::Initialize() lives behind the liblldb.dll thunk
that the import binding fires against, so the loader still has to run
from the binary that statically links lldbHost (lldb.exe / lldb-dap.exe)
before the first SB call lands.



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