[pushed] Mention Windows scheduler-locking in NEWS (Re: [pushed 17/28] Windows gdb: Enable "set scheduler-locking on")

[Pedro Alves <pedro@palves.net>]

On 2026-04-24 21:44, Pedro Alves wrote:
> 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.
> 

I had the news about scheduler-locking in the same patch as the non-stop support
news, back in the v2 non-stop series.

Since scheduler-locking is already merged, I've now split the NEWS bit about it
to its own patch and merged it, as below.

Pedro Alves

From 8e78d43dbcd122e852d59abe29c8d6aeb6c04925 Mon Sep 17 00:00:00 2001
From: Pedro Alves <pedro@palves.net>
Date: Mon, 22 May 2023 19:16:30 +0100
Subject: [PATCH] Mention Windows scheduler-locking in NEWS

Add a note to gdb/NEWS mentioning Windows native target
scheduler-locking support.

Approved-By: Eli Zaretskii <eliz@gnu.org>
Change-Id: Id0e28525c06e57120c47b07f978581d1627d70f3
commit-id:ba1d5868
---
 gdb/NEWS | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/gdb/NEWS b/gdb/NEWS
index 18f1b6308da..e233906153a 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -72,6 +72,9 @@
   automatically set to UTF-8.  (Users can use the Windows 'chcp'
   command to change the output codepage of the console.)
 
+* The Windows native target now supports scheduler-locking.  E.g.,
+  "set scheduler-locking on" now works.  Previously it gave an error.
+
 * New targets
 
 GNU/Linux/MicroBlaze (gdbserver) microblazeel-*linux*

base-commit: 20699002b9630ed90b2518735c7d945e89445a83
-- 
2.53.0