mirror of
https://github.com/reactos/reactos.git
synced 2026-05-29 21:19:51 +08:00
a4621bb280
The `ThreadNameInformation` (#38) class is the Windows 10.1607+ way of assigning a human-readable name (i.e. description) to a given thread object, that is visible to debuggers and diagnostic tools (e.g. WinDbg `!thread` command, Process Explorer ...), which is useful for debugging scenarios.[^1] Before this, the only way to assign a name to a thread for debugging purposes was to raise a specific exception, that had to be caught and interpreted by a supported debugger.[^2][^3] When the thread object is being deleted (`kill.c!PspDeleteThread()`), free the thread name if set (courtesy of Ahmed Arif, PR #8796). References: [^1]: https://learn.microsoft.com/en-us/visualstudio/debugger/tips-for-debugging-threads [^2]: https://learn.microsoft.com/en-us/archive/blogs/stevejs/naming-threads-in-win32-and-net [^3]: https://ofekshilon.com/2009/04/10/naming-threads/
====================
ReactOS Tests
====================
This directory contains various tests for ReactOS.
Make sure you also have a copy of the rest of the ReactOS
source before you attempt to build anything in this module.
It is to be placed under "modules" subdirectory of a trunk checkout.
The module requires to be enabled during the "configure" process.
To include the module in your build folder, run the configure script with the flags -DENABLE_ROSTESTS=1
# For Windows users
configure.cmd -DENABLE_ROSTESTS=1
# For UNIX users
./configure.sh -DENABLE_ROSTESTS=1