<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Thread identification in Glance in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/thread-identification-in-glance/m-p/2497215#M20252</link>
    <description>pthread_self() generates the ID at compile time (yukkie). You could use the pstat() system call and get the real TID at runtime. much more useful. Your interested in lwp_lwpid.&lt;BR /&gt;&lt;BR /&gt;Andy</description>
    <pubDate>Thu, 22 Feb 2001 19:11:46 GMT</pubDate>
    <dc:creator>Andy Monks</dc:creator>
    <dc:date>2001-02-22T19:11:46Z</dc:date>
    <item>
      <title>Thread identification in Glance</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/thread-identification-in-glance/m-p/2497213#M20250</link>
      <description>Using pthreads in HP-UX 11.00, we use pthread_self() to get a threads own thread ID (TID) for tracing. Since these TIDs are only unique for threads within the same process, the ints returned are always low numbers, i.e. 1-2 digits.&lt;BR /&gt;&lt;BR /&gt;However when looking at our thread stats with Glance the TIDs all have 4-5 digits, looking much more like process IDs. Is there any way we can match these two to know which thread is doing what?</description>
      <pubDate>Thu, 22 Feb 2001 10:30:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/thread-identification-in-glance/m-p/2497213#M20250</guid>
      <dc:creator>Anthony Leonard</dc:creator>
      <dc:date>2001-02-22T10:30:32Z</dc:date>
    </item>
    <item>
      <title>Re: Thread identification in Glance</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/thread-identification-in-glance/m-p/2497214#M20251</link>
      <description>There is no direct corralation between tid and the index number. However, as TID's are allocated seqentially, it should tie up nicely, until they get to 30000, when they wrap around back to 0.</description>
      <pubDate>Thu, 22 Feb 2001 19:03:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/thread-identification-in-glance/m-p/2497214#M20251</guid>
      <dc:creator>Andy Monks</dc:creator>
      <dc:date>2001-02-22T19:03:55Z</dc:date>
    </item>
    <item>
      <title>Re: Thread identification in Glance</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/thread-identification-in-glance/m-p/2497215#M20252</link>
      <description>pthread_self() generates the ID at compile time (yukkie). You could use the pstat() system call and get the real TID at runtime. much more useful. Your interested in lwp_lwpid.&lt;BR /&gt;&lt;BR /&gt;Andy</description>
      <pubDate>Thu, 22 Feb 2001 19:11:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/thread-identification-in-glance/m-p/2497215#M20252</guid>
      <dc:creator>Andy Monks</dc:creator>
      <dc:date>2001-02-22T19:11:46Z</dc:date>
    </item>
  </channel>
</rss>

