aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPedro Alves <pedro@palves.net>2023-05-11 23:07:33 +0100
committerPedro Alves <pedro@palves.net>2024-05-10 11:25:59 +0100
commit5ad78cc6246a4a35a6bb51cb0dcc28d6c49aacd0 (patch)
tree0f326864dc10aa4cd91953b116531e30d28b4f05
parent02ff02e05f6706d7ba78ef8bd4a819cc00bea66b (diff)
downloadfsf-binutils-gdb-5ad78cc6246a4a35a6bb51cb0dcc28d6c49aacd0.zip
fsf-binutils-gdb-5ad78cc6246a4a35a6bb51cb0dcc28d6c49aacd0.tar.gz
fsf-binutils-gdb-5ad78cc6246a4a35a6bb51cb0dcc28d6c49aacd0.tar.bz2
Windows gdb: Enable "set scheduler-locking on"
Surprisingly (to me), enabling scheduler locking on Windows currently fails: (gdb) set scheduler-locking on Target 'native' cannot support this command. The backend itself does support scheduler-locking. This patch implements windows_nat_target::get_thread_control_capabilities so that the core knows schedlocking works for this target. Change-Id: Ie762d3768fd70e4ac398c8bcc03c3213bfa26a6a
-rw-r--r--gdb/windows-nat.c3
1 files changed, 3 insertions, 0 deletions
diff --git a/gdb/windows-nat.c b/gdb/windows-nat.c
index d783148..2913da6 100644
--- a/gdb/windows-nat.c
+++ b/gdb/windows-nat.c
@@ -261,6 +261,9 @@ struct windows_nat_target final : public x86_nat_target<inf_child_target>
void close () override;
+ thread_control_capabilities get_thread_control_capabilities () override
+ { return tc_schedlock; }
+
void attach (const char *, int) override;
bool attach_no_wait () override