For a very long time, it has been possible to name threads visible in debuggers: How to: Set a Thread Name in Native Code.
In the mean time, under Windows 10, you can both Get and Set the thread name. This brings native applications on par with with .NET where this has always been possible. Chrome uses these new API calls.
Which means I have some reading to do:
- [WayBack] Thread Naming in Windows: Time for Something Better | Random ASCII – tech blog of Bruce Dawson
- [WayBack] Issue 2713773002: ShowThreadNames tool to get thread ID/name pairs in a Chrome process – Code Review
- [WayBack] GetThreadDescription function (processthreadsapi.h) | Microsoft Docs
- [WayBack] SetThreadDescription function (processthreadsapi.h) | Microsoft Docs
- [WayBack] Issue 2692213003: Use Windows 10 thread naming API, SetThreadDescription – Code Review
- [WayBack] c++ – How to get the name of a Win32 Thread? – Stack Overflow
- [WayBack] Thread.Name Property (System.Threading) | Microsoft Docs
- [WayBack] c# – Get StartAddress of win32 thread from another process – Stack Overflow
–jeroen
