[all-commits] [llvm/llvm-project] 84d12c: [lldb] Implement delayed breakpoints

[Felipe de Azevedo Piovezan via All-commits]

  Branch: refs/heads/users/felipepiovezan/delayed_bps_p3
  Home:   https://github.com/llvm/llvm-project
  Commit: 84d12c8216565fabd1cc2eede0ff0577beceecdd
      https://github.com/llvm/llvm-project/commit/84d12c8216565fabd1cc2eede0ff0577beceecdd
  Author: Felipe de Azevedo Piovezan <fpiovezan at apple.com>
  Date:   2026-04-27 (Mon, 27 Apr 2026)

  Changed paths:
    M lldb/include/lldb/Target/Process.h
    M lldb/source/Plugins/Process/MacOSX-Kernel/ProcessKDP.cpp
    M lldb/source/Plugins/Process/Utility/StopInfoMachException.cpp
    M lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp
    M lldb/source/Plugins/Process/scripted/ScriptedProcess.cpp
    M lldb/source/Plugins/Process/scripted/ScriptedThread.cpp
    M lldb/source/Target/Process.cpp
    M lldb/source/Target/TargetProperties.td
    M lldb/source/Target/ThreadPlanStepOverBreakpoint.cpp

  Log Message:
  -----------
  [lldb] Implement delayed breakpoints

This patch changes the Process class so that it delays *physically*
enabling/disabling breakpoints until the process is about to
resume/detach/be destroyed, potentially reducing the packets transmitted
by batching all breakpoints together.

Most classes only need to know whether a breakpoint is "logically"
enabled, as opposed to "physically" enabled (i.e. the remote server has
actually enabled the breakpoint). However, lower level classes like
derived Process classes, or StopInfo may actually need to know whether
the breakpoint was physically enabled. As such, this commit also adds a
"IsPhysicallyEnabled" API.

https://github.com/llvm/llvm-project/pull/192910



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