Re: Program-assigned thread names on Windows

LRN
2016-07-23T09:43:25Z

[-- Attachment #1.1.1: Type: text/plain, Size: 1304 bytes --]

On 23.07.2016 12:33, Eli Zaretskii wrote:
> On 23.07.2016 12:25, LRN wrote:
>> The attached patch adds thread naming support on Windows.
>>
>> This works as documented[1] on MSDN - by catching a specific
>> exception that the program throws.
>>
>> Setting thread name this way is supported by glib[2] and winpthreads[3] at
>> least, as well as any program developed with MS toolchain (because WinDbg
>> supported this for a long time).
>>
>> [1] https://msdn.microsoft.com/en-us/library/xcb2z8hs.aspx
>> [2] https://git.gnome.org/browse/glib/commit/glib/gthread-
>> win32.c?id=e118856430a798bbc529691ad235fd0b0684439d
>> [3] https://sourceforge.net/p/mingw-w64/mingw-w64/ci
>> /0d95c795b44b76e1b60dfc119fd93cfd0cb35816/
>>
>
> Thanks. But I don't think what that means in terms of the "thread
> name", "thread find", and "info threads" commands in GDB. Can you
> tell?
>

"info thread" will show the thread name, if it is set

"thread name" will change the thread name (but the debugee will not be
aware of that; i haven't looked for a way to communicate name change
back to the debugee, and i doubt that such way exists)

"thread find" will be able to find threads by their name, if they have it set

--
O< ascii ribbon - stop html email! - www.asciiribbon.org

[-- Attachment #1.1.2: 0x6759BA74.asc --]