================
@@ -143,8 +142,14 @@
NativeRegisterContextWindows::CreateHostNativeRegisterContextWindows(
NativeRegisterContextWindows_arm64::NativeRegisterContextWindows_arm64(
const ArchSpec &target_arch, NativeThreadProtocol &native_thread)
- : NativeRegisterContextWindows(native_thread,
- CreateRegisterInfoInterface(target_arch)) {}
+ : NativeRegisterContextRegisterInfo(
+ native_thread, CreateRegisterInfoInterface(target_arch)) {
+ // Currently, there is no API to query the maximum supported hardware
+ // breakpoints and watchpoints on Windows. The values set below are based
----------------
labath wrote:
In principle, there's nothing stopping you from launching a dummy process just
for the purpose of testing the debug API. I noticed that this is what linux
`strace` does when it tries to determine the host kernel capabilities. Windows
makes this slightly trickier as you can't just call `fork` -- you need an
actual executable -- but the same principle holds. (I'm not saying we need to
do this here, I'm just throwing the idea out there.)
https://github.com/llvm/llvm-project/pull/108072
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
