[Bug win32/29050] New: Read thread names from Windows inferior

[Bug win32/29050] New: Read thread names from Windows inferior

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=29050

            Bug ID: 29050
           Summary: Read thread names from Windows inferior
           Product: gdb
           Version: 11.1
            Status: NEW
          Severity: normal
          Priority: P2
         Component: win32
          Assignee: unassigned at sourceware dot org
          Reporter: tromey at sourceware dot org
  Target Milestone: ---

Windows 10 adds SetThreadDescription, so a thread can set its name.
These can be retrieved with GetThreadDescription (I think).
gdb could use these APIs when available -- both to name its own
threads (though this is complicated because the libstdc++ patch
isn't in), and also when examining an inferior.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug win32/29050] Read thread names from Windows inferior

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=29050

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|unassigned at sourceware dot org   |tromey at sourceware dot org

--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
I ended up writing patches for this.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug win32/29050] Read thread names from Windows inferior

[cvs-commit at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=29050

--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=1ea519ec192d68397d8b22f55072fc7ba0c5e36c

commit 1ea519ec192d68397d8b22f55072fc7ba0c5e36c
Author: Tom Tromey <tromey@adacore.com>
Date:   Wed Apr 13 08:12:52 2022 -0600

    Set the worker thread name on Windows

    This patch is a bit different from the rest of the series, in that it
    is a change to gdb's behavior on the host.  It changes gdb's thread
    pool to try to set the thread name on Windows, if SetThreadDescription
    is available.

    This is part of PR win32/29050.

    This patch isn't likely to be useful to many people in the short term,
    because the Windows port of the libstdc++ thread code is not upstream.
    (AdaCore uses it, and sent it upstream, but it did not land, I don't
    know why.)  However, if that patch does ever go in, or presumably if
    you build using some other C++ runtime library, then this will be
    useful.

    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29050

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug win32/29050] Read thread names from Windows inferior

[cvs-commit at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=29050

--- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=8bbdbd6985d8d7615bab69f97f07e8bb78fb98f8

commit 8bbdbd6985d8d7615bab69f97f07e8bb78fb98f8
Author: Tom Tromey <tromey@adacore.com>
Date:   Wed Apr 13 08:45:34 2022 -0600

    Use GetThreadDescription on Windows

    Windows 10 introduced SetThreadDescription and GetThreadDescription, a
    simpler way to set a thread's name.  This changes gdb and gdbserver to
    use this convention when it is available.

    This is part of PR win32/29050.

    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29050

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug win32/29050] Read thread names from Windows inferior

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=29050

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
   Target Milestone|---                         |13.1
         Resolution|---                         |FIXED

--- Comment #4 from Tom Tromey <tromey at sourceware dot org> ---
Fixed.

-- 
You are receiving this mail because:
You are on the CC list for the bug.