[PATCH v2 0/2] Use +threadname channel for both methods of thread renaming.

[Brendan Shanks]

Currently, the two methods of setting thread names in Windows
(SetThreadDescription() and the 0x406D1388 exception) log to different channels.

I think it would be useful for these to both log to the same +threadname
channel. My thinking is that this would be similar to +debugstr, in that
all messages are human-readable descriptions which would be useful for
debugging crashes.

v2: Specify whether thread ID or handle is being renamed.

Brendan Shanks (2):
  kernelbase: Use +threadname channel for SetThreadDescription().
  ntdll: Use +threadname channel for thread rename exceptions.

 dlls/kernelbase/thread.c   | 6 +++++-
 dlls/ntdll/signal_arm.c    | 7 ++++++-
 dlls/ntdll/signal_arm64.c  | 7 ++++++-
 dlls/ntdll/signal_i386.c   | 7 ++++++-
 dlls/ntdll/signal_x86_64.c | 8 ++++++--
 5 files changed, 29 insertions(+), 6 deletions(-)

-- 
2.30.1 (Apple Git-130)