In my system pthread_t type is "unsigned long int" /usr/include/x86_64-linux-gnu/bits/pthreadtypes.h:typedef unsigned long int pthread_t Void *(*start_routine) (void *), void *arg) Pthread_self returns the same ID, what pthread_create stores in the first argument "thread" int pthread_create(pthread_t *thread, const pthread_attr_t *attr, The abstract type of pthread_t is implementation dependent.īefore returning, a successful call to pthread_create() stores the ID of the new thread in the buffer pointed to by thread this identifier is used to refer to the thread in subsequent calls to other pthread functions. This ID is used to identify the thread for other pthread functions. It is assigned the ID of the newly created thread. man 3 pthread_selfįor pthread_create(), the first argument is of type pthread_t. Please check man pages for pthread_self and pthread_create. Pthread_named_by_parent.Pthread_self() returns the ID of the thread. Making sure the parent thread gave the pthread a name.įprintf(stdout, "I am thread with ID '%lu', my name is '%s' and my parent gave me my name\n", tid, thread_name ) Ĭonst int setname_rv = pthread_setname_np(thread_info.thread_id, "Bob Marley") Added an artificial delay for the sake of the example. #include is needed for the resolution of unsigned int sleep(unsigned int seconds) The next code, creates a pthread and the parent gives the thread a meaningful name. The pthread_join() function suspends execution of the calling thread until the target thread terminates, unless the target thread has already terminated.Ĭonst int join_rv = pthread_join(thread_info.thread_id, NULL) Įxample 2: The parent decides for the pthread name so we print pthread_t as an unsigned long intįprintf(stdout, "I am thread with ID '%lu', my name is '%s' and I gave me my name by myself\n", tid, thread_name ) Ĭonst int create_rv = pthread_create(&(thread_info.thread_id), NULL, &self_named_thread, (void *) &thread_info) Usually pthread_t is defined as follows: This function always succeeds, returning the calling thread's ID. Struct thread_info_t *thread_info = (struct thread_info_t *) data Ĭonst int setname_rv = pthread_setname_np(thread_info->thread_id, "Tom Hanks") Ĭhar thread_name Ĭonst int getname_rv = pthread_getname_np(thread_info->thread_id, thread_name, MAX_LENGTH_PTHREAD_NAME) We know that the input data pointer is pointing to a thread_info_t so we are casting it to the right type. This is the thread that will be called by pthread_create() and it will be executed by the new thread. The thread name is a meaningful C language string, whose length is restricted to 16 characters, including the terminating null byte. #include is needed for the resolution of EXIT_SUCCESS warning: implicit declaration of function ‘pthread_getname_np’ warning: implicit declaration of function ‘pthread_setname_np’ #define _GNU_SOURCE is needed for the resolution of the following warnings The following code, creates a pthread which later, it will give itself a meaningful name. Pthread_named_by_parent.c (compressed) (344 downloads)Įxample 1: The pthread decides for its name Pthread_self_named.c (compressed) (384 downloads) Naming a pthread using meaningful names, can be a very useful feature for debugging multi-threaded applications as it can make your logs very informative.įor this reason, we are presenting two examples demonstrating the use of names in pthreads. 29 September 2017 in C / C++ tagged _GNU_SOURCE / C/C++ / C++ / errno / pthread_create / pthread_getname_np / pthread_join / pthread_self / pthread_setname_np / pthread_t by Tux
0 kommentar(er)
