[Bug backtrace/16568] New: BT command should display custom thread name, now that pthread_setname_np() is widely supported.

["gziemski at mac dot com" <sourceware-bugzilla at sourceware dot org>]

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

            Bug ID: 16568
           Summary: BT command should display custom thread name, now that
                    pthread_setname_np() is widely supported.
           Product: gdb
           Version: 7.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: backtrace
          Assignee: unassigned at sourceware dot org
          Reporter: gziemski at mac dot com

Created attachment 7406
  --> https://sourceware.org/bugzilla/attachment.cgi?id=7406&action=edit
Linux version of pthread_setname_np() test case

BT command should display custom thread name, now that pthread_setname_np() is
widely supported.

For Oracle JDK we have https://bugs.openjdk.java.net/browse/JDK-7102541 where
we'll be adding support to name native threads. This is now doable since
pthread_setname_np() is supported on Mac OS X (since 10.5) and BSD, Linux
(since glib v. 2.12) and Solaris (since S12 and S11.4)

However, the names of the threads are curiously absent from "BT" command, and
they are only show for "info threads" command.

LLDB will happily show the threads names for "bt all", which is quite useful.

It would be nice if GDB also showed the thread names for its corresponding "t a
a bt" command.

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