This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Program-assigned thread names on Windows
- From: Eli Zaretskii <eliz at gnu dot org>
- To: LRN <lrn1986 at gmail dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Sat, 23 Jul 2016 12:33:04 +0300
- Subject: Re: Program-assigned thread names on Windows
- Authentication-results: sourceware.org; auth=none
- References: <5052d495-ea40-b364-96ea-9e68c90bd747@gmail.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: LRN <lrn1986@gmail.com>
> Date: Sat, 23 Jul 2016 12:25:15 +0300
>
> 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?