diff options
author | Jonas Devlieghere <jonas@devlieghere.com> | 2025-07-03 11:17:19 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2025-07-03 11:17:19 -0700 |
commit | 378f248934d603e3fba9d958d2db997814d057d5 (patch) | |
tree | d528925e5138678456f77176f845a12f7696ddc4 /clang/lib/CodeGen/CodeGenModule.cpp | |
parent | 1e76f012db3ccfaa05e238812e572b5b6d12c17e (diff) | |
download | llvm-378f248934d603e3fba9d958d2db997814d057d5.zip llvm-378f248934d603e3fba9d958d2db997814d057d5.tar.gz llvm-378f248934d603e3fba9d958d2db997814d057d5.tar.bz2 |
[lldb] Add SB API to make a breakpoint a hardware breakpoint (#146602)
This adds SBBreakpoint::SetIsHardware, allowing clients to mark an
existing breakpoint as a hardware breakpoint purely through the API.
This is safe to do after creation, as the hardware/software distinction
doesn't affect how breakpoint locations are selected.
In some cases (e.g. when writing a trap instruction would alter program
behavior), it's important to use hardware breakpoints. Ideally, we’d
extend the various `Create` methods to support this, but given their
number, this patch limits the scope to the post-creation API. As a
workaround, users can also rely on target.require-hardware-breakpoint or
use the `breakpoint set` command.
rdar://153528045
Diffstat (limited to 'clang/lib/CodeGen/CodeGenModule.cpp')
0 files changed, 0 insertions, 0 deletions