public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug threads/15824] New: Can't get threads name from info threads with linux kernel version below 2.6.32
@ 2013-08-08  3:53 huangjiangwei at gmail dot com
  2013-08-12  9:05 ` [Bug threads/15824] " huangjiangwei at gmail dot com
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: huangjiangwei at gmail dot com @ 2013-08-08  3:53 UTC (permalink / raw)
  To: gdb-prs

http://sourceware.org/bugzilla/show_bug.cgi?id=15824

            Bug ID: 15824
           Summary: Can't get threads name from info threads with linux
                    kernel version below 2.6.32
           Product: gdb
           Version: 7.6
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: threads
          Assignee: unassigned at sourceware dot org
          Reporter: huangjiangwei at gmail dot com

Created attachment 7136
  --> http://sourceware.org/bugzilla/attachment.cgi?id=7136&action=edit
patches for print thread name correctly

OS:Linux  2.6.32-220.23.2.ali1089.el5.x86_64 
GNU gdb (GDB) 7.6
Under linux kernel 2.6.32( or below version) there is no proc file named
/proc/$pid/task/$tid/comm.
So info threads can't print correct thread names. 
This can be solve by using procfs /proc/$pid/task/$tid/status.
Files attached are the patches.

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


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2013-08-13 14:44 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-08-08  3:53 [Bug threads/15824] New: Can't get threads name from info threads with linux kernel version below 2.6.32 huangjiangwei at gmail dot com
2013-08-12  9:05 ` [Bug threads/15824] " huangjiangwei at gmail dot com
2013-08-12  9:07 ` huangjiangwei at gmail dot com
2013-08-13 14:44 ` tromey at redhat dot com

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).