In a Linux C program, how do I print the thread id of a thread created by the pthread library? For example like how we can get pid of a process by getpid()
.

- 9,146
- 4
- 29
- 50

- 1,749
- 4
- 13
- 22
-
See also: [Difference between __NR_gettid and SYS_gettid](https://stackoverflow.com/a/22351167/4561887) and [getting error in c program "undefined reference to gettid"](https://stackoverflow.com/a/63827823/4561887). – Gabriel Staples Sep 22 '21 at 21:34
12 Answers
What? The person asked for Linux specific, and the equivalent of getpid()
. Not BSD or Apple. The answer is gettid()
and returns an integral type. You will have to call it using syscall()
, like this:
#include <sys/types.h>
#include <unistd.h>
#include <sys/syscall.h>
....
pid_t x = syscall(__NR_gettid);
While this may not be portable to non-linux systems, the threadid is directly comparable and very fast to acquire. It can be printed (such as for LOGs) like a normal integer.

- 3,482
- 3
- 38
- 50

- 4,050
- 2
- 20
- 18
-
18
-
2The person asked about something that worked on Linux. Doing so in a portable way seems to me like the preferable way to do it. If portability doesn't count for anything then I guess Linux is really becoming the new Windows... – Jasper Siepkes Dec 19 '19 at 11:26
-
4@Jasper Siepkes You are missing the point. He asked for a LINUX call that was the equivalent of getpid() for threads. That is gettid(). The question didn't ask about portability or POSIX. Too many people want to show off and try and teach rather than asking the question as asked. pthread_self() does not return the kernel thread id and it not manipulatable in a way that makes for easy printing. Also, pthread_self is likely a pointer and should not be manipulated, only compared with pthread_equal(). The question asked for an ID you can print, and that's gettid(). – Evan Langlois Dec 20 '19 at 12:39
-
4@EvanLanglois He's working with the pthread library, literally the POSIX thread library. Making a POSIX compatible answer not that weird. "He asked for a LINUX call that was the equivalent of getpid() for threads." No, `getpid()` was given as an example. It didn't say the semantics were a hard specification. Making people aware of doing things in a POSIX compatible way so other communities besides Linux (like FreeBSD, Illumos, OS X, etc.) can benefit from them is not "showing off". Like I said I guess Linux has really become the next Windows. – Jasper Siepkes Mar 30 '20 at 16:20
-
1Can you explain and add to your answer how and when one must use `syscall()`, and what the `__NR_` part comes from and means, and where we can see a list of possible values to pass into `syscall()`? – Gabriel Staples Sep 22 '21 at 21:24
-
Also, I see a different answer with `syscall(SYS_gettid)`. How is that the same or different from `syscall(__NR_gettid)`? – Gabriel Staples Sep 22 '21 at 21:25
-
See also: [Difference between __NR_gettid and SYS_gettid](https://stackoverflow.com/a/22351167/4561887) and [getting error in c program "undefined reference to gettid"](https://stackoverflow.com/a/63827823/4561887). – Gabriel Staples Sep 22 '21 at 21:34
-
Those are constants defined in header files, defined by the linux kernel. As to NR vs SYS, I would have to Google that. Maybe it has to do with process groups? I dont know – Evan Langlois Sep 24 '21 at 00:08
-
2On Linux Ubuntu 18.04 with `gcc --version` `gcc (Ubuntu 8.4.0-1ubuntu1~18.04) 8.4.0` I had to also add `#define _GNU_SOURCE` above all of the includes in order for `syscall()` to be defined. I learned that from the example at the bottom of this documentation here: https://man7.org/linux/man-pages/man2/syscall.2.html. – Gabriel Staples Sep 24 '21 at 00:56
-
The value returned by `gettid()` is not the same as the value returned by `pthread_self()`, If you want a thread id that pthread functions can use, you want to call pthread_self(). – Robin Davies Apr 01 '23 at 20:16
-
@RobinDavies Is this an April Fool's joke? The question asks for a *printable* id like you would get with getpid(). Good luck printing or comparing pthread_self()'s return value. – Evan Langlois Apr 07 '23 at 21:52
pthread_self()
function will give the thread id of current thread.
pthread_t pthread_self(void);
The pthread_self()
function returns the Pthread handle of the calling thread. The pthread_self() function does NOT return the integral thread of the calling thread. You must use pthread_getthreadid_np()
to return an integral identifier for the thread.
NOTE:
pthread_id_np_t tid;
tid = pthread_getthreadid_np();
is significantly faster than these calls, but provides the same behavior.
pthread_id_np_t tid;
pthread_t self;
self = pthread_self();
pthread_getunique_np(&self, &tid);

- 19,989
- 5
- 106
- 123

- 2,911
- 3
- 20
- 29
-
46The original question was about Linux. Linux does not include the _np functions. (It doesn't include their man pages, I didn't check any further than that.) – Trade-Ideas Philip Apr 24 '14 at 04:30
-
-
@Bleater Can you please provide the official documentation for `pthread_threadid_np`. Am in need to use for a project, so need to check on the reliability of that API in iOS and OSX platforms. Referred the link at http://www.opensource.apple.com/source/Libc/Libc-583/pthreads/pthread.h but not sure if they are the right one. – Vivek Maran Feb 23 '15 at 14:26
-
@Vivek I don't have any link to official docs, just the header you link and the source at http://www.opensource.apple.com/source/Libc/Libc-583/pthreads/pthread.c – bleater Feb 27 '15 at 01:17
-
15@Trade-IdeasPhilip - To clarify, `_np` means non-portable. Linux has its own `_np` stuff, but it doesn't include Apple's `pthread_getthreadid_np`. – Josh Kelley Oct 28 '15 at 17:18
-
1Some important note: A `pthread_t` is a kind of pointer in Linux. So if you run the same program multiple times, you may see the *same* `pthread_t`, while the actual threads are different. Thus printing the `pthread_t` does not help very much. – U. Windl Aug 10 '20 at 10:37
As noted in other answers, pthreads does not define a platform-independent way to retrieve an integral thread ID.
On Linux systems, you can get thread ID thus:
#include <sys/types.h>
pid_t tid = gettid();
On many BSD-based platforms, this answer https://stackoverflow.com/a/21206357/316487 gives a non-portable way.
However, if the reason you think you need a thread ID is to know whether you're running on the same or different thread to another thread you control, you might find some utility in this approach
static pthread_t threadA;
// On thread A...
threadA = pthread_self();
// On thread B...
pthread_t threadB = pthread_self();
if (pthread_equal(threadA, threadB)) printf("Thread B is same as thread A.\n");
else printf("Thread B is NOT same as thread A.\n");
If you just need to know if you're on the main thread, there are additional ways, documented in answers to this question how can I tell if pthread_self is the main (first) thread in the process?.
pid_t tid = syscall(SYS_gettid);
Linux provides such system call to allow you get id of a thread.

- 181
- 1
- 3
-
3As per [this answer](https://stackoverflow.com/a/21280941/603003), you need `#include
` and `#include – ComFreek Dec 01 '20 at 13:49` for this.
This single line gives you pid , each threadid and spid.
printf("before calling pthread_create getpid: %d getpthread_self: %lu tid:%lu\n",getpid(), pthread_self(), syscall(SYS_gettid));

- 133
- 1
- 8
I think not only is the question not clear but most people also are not cognizant of the difference. Examine the following saying,
POSIX thread IDs are not the same as the thread IDs returned by the Linux specific
gettid()
system call. POSIX thread IDs are assigned and maintained by the threading implementation. The thread ID returned bygettid()
is a number (similar to a process ID) that is assigned by the kernel. Although each POSIX thread has a unique kernel thread ID in the Linux NPTL threading implementation, an application generally doesn’t need to know about the kernel IDs (and won’t be portable if it depends on knowing them).Excerpted from: The Linux Programming Interface: A Linux and UNIX System Programming Handbook, Michael Kerrisk
IMHO, there is only one portable way that pass a structure in which define a variable holding numbers in an ascending manner e.g. 1,2,3...
to per thread. By doing this, threads' id can be kept track. Nonetheless, int pthread_equal(tid1, tid2)
function should be used.
if (pthread_equal(tid1, tid2)) printf("Thread 2 is same as thread 1.\n");
else printf("Thread 2 is NOT same as thread 1.\n");

- 18,731
- 3
- 79
- 101
-
The `gettid()` is actually a good suggestion, thank you! However, I needed to follow the answer by Sergey L. here: https://stackoverflow.com/a/21280941/2430526 – SRG Mar 27 '19 at 22:06
pthread_getthreadid_np
wasn't on my Mac os x. pthread_t
is an opaque type. Don't beat your head over it. Just assign it to void*
and call it good. If you need to printf
use %p
.
-
1Yes, this works. All I need is to print it for debugging so 0x23423423423abcdef is as helpful as tid=1234. Thank you! – Qi Fan Jul 29 '16 at 23:22
There is also another way of getting thread id. While creating threads with
int pthread_create(pthread_t * thread, const pthread_attr_t * attr, void * (*start_routine)(void *), void *arg);
function call; the first parameter pthread_t * thread
is actually a thread id (that is an unsigned long int defined in bits/pthreadtypes.h). Also, the last argument void *arg
is the argument that is passed to void * (*start_routine)
function to be threaded.
You can create a structure to pass multiple arguments and send a pointer to a structure.
typedef struct thread_info {
pthread_t thread;
//...
} thread_info;
//...
tinfo = malloc(sizeof(thread_info) * NUMBER_OF_THREADS);
//...
pthread_create (&tinfo[i].thread, NULL, handler, (void*)&tinfo[i]);
//...
void *handler(void *targs) {
thread_info *tinfo = targs;
// here you get the thread id with tinfo->thread
}

- 358
- 1
- 6
For different OS there is different answer. I find a helper here.
You can try this:
#include <unistd.h>
#include <sys/syscall.h>
int get_thread_id() {
#if defined(__linux__)
return syscall(SYS_gettid);
#elif defined(__FreeBSD__)
long tid;
thr_self(&tid);
return (int)tid;
#elif defined(__NetBSD__)
return _lwp_self();
#elif defined(__OpenBSD__)
return getthrid();
#else
return getpid();
#endif
}

- 19
- 1
Platform-independent way (starting from c++11) is:
#include <thread>
std::this_thread::get_id();

- 525
- 6
- 10
-
1this probably isnt as "platform independent" as you think. on my implementation it resolves to a `pthread_t`. On a mac that will be a pointer and on Linux an integer. It also doesn't reflect the "native" id you might see in `top` for example. Something to be aware of, but maybe its fine for some uses. – Brad Allred Sep 28 '18 at 22:20
-
1In C11 (the question was about C) you would use thrd_current() from threads.h – jerry Dec 05 '18 at 13:58
You can also write in this manner and it does the same. For eg:
for(int i=0;i < total; i++)
{
pthread_join(pth[i],NULL);
cout << "SUM of thread id " << pth[i] << " is " << args[i].sum << endl;
}
This program sets up an array of pthread_t and calculate sum on each. So it is printing the sum of each thread with thread id.

- 83
- 1
- 8
-
It does not answer the question, and even the description for the code is wrong! – U. Windl Aug 10 '20 at 10:41