Sponsored Content
Top Forums Programming pthread question : global variable not updated Post 302609897 by sanjayc on Tuesday 20th of March 2012 02:37:21 PM
Old 03-20-2012
pthread question : global variable not updated

Hi,
I wrote the following program to understand mutexes. If I run the program , number of threads is shown as zero, even after creating one thread. When running with gdb, it works fine.

The function process is used to update global variable (used to keep track of threads). It looks like the second instance of display (which displays number of threads ) is running before the counter gets incremented. If I add a pthread_join in main thread it works (main thread waits for created thread to complete). Is there a better way to address this and is my understanding correct? Thanks

Code:
#include <stdio.h>
#include <stdlib.h>
#include <pthread.h>

int num_thread=0;
 pthread_mutex_t threadcount=PTHREAD_MUTEX_INITIALIZER;

void *process( )
  {
  pthread_mutex_lock(&threadcount);
   num_thread++;
  pthread_mutex_unlock(&threadcount);
   }

void display()
  {
    pthread_mutex_lock(&threadcount);
   printf("num of threads %d \n",num_thread);
  pthread_mutex_unlock(&threadcount);
   }

 int main()
{
   pthread_t tid1, tid2;
    int t;
 
    display();
    pthread_create(&tid1,NULL,process,&t);
    display();
   return 0;
 
  }

Moderator's Comments:
Mod Comment Please use code tags for posting code.

Last edited by Corona688; 03-20-2012 at 04:40 PM..
 

10 More Discussions You Might Find Interesting

1. AIX

pthread lock question

Is it possible that the function "pthread_cond_broadcast" block itself and the function "pthread_cond_wait" unblock in multi-threads programming ? The operating system is AIX 5.2, its maintenance level is : 5.2.0.4, VisualAge C++ 6.0. Thanks (0 Replies)
Discussion started by: Frank2004
0 Replies

2. AIX

pthread performance question

Running dedicated on AIX with 4 processors, creating 4 threads, each with equal work to do, only runs about 20% faster than 1 thread with all of the work. Test case has no blocking but does share memory for read access only. Any ideas why I'm only seeing 20% gain? Is this typical on AIX? ... (1 Reply)
Discussion started by: ldarden
1 Replies

3. Shell Programming and Scripting

Global variable

I have written a shell scritp in which i am using a variable which is declared before a while loop and i am updaitng the variable in while loop and want to use its updated value outside the loop. I am not able to do so, b'coz the scope of the variable is limited to the while loop only and when i am... (5 Replies)
Discussion started by: deepanshu
5 Replies

4. Programming

a question about pthread performance

Hello, I run my pthread code on Linux with 4 processors. However, the speed up is only 2 times. The code is about solving equation (G+s(i)C)z(i)=B*us(i), i=1,...,n. Here G,C are m*m matrix, B*us(i) is a m*1 vector and s(i) are n different numbers. I need to solve the equation n times to... (1 Reply)
Discussion started by: mgig
1 Replies

5. Shell Programming and Scripting

Help with Global Variable

Hi Guyz, I have a requirement like, i have to run a script every hour to count the number of errors encountered. At the end of the day, i need to send them the total number of errors, that have ocurred the entire day. For eg. if 10 errors occurred for starting 1 hr, 5 for next 1 hr, so on.... (1 Reply)
Discussion started by: DTechBuddy
1 Replies

6. Programming

pthread and mutex question

Hello, I have got some issue with the struct variable with passed arguments the variable in the sturct is only recognize the last value their assigned to I'm pretty confused why the mutex didn't work out here is my program: #include<stdio.h> #include<pthread.h> pthread_mutex_t lock... (3 Replies)
Discussion started by: michael23
3 Replies

7. Shell Programming and Scripting

Global variable value

Hi All, Im new to shell scripting. I am running EgA.sh and setting one global variable XYZ=0 . Also calling another EgB.sh from EgA.sh, changing the value of XYZ=10 but after executing EgB.sh, value of XYZ is still 0. Im expecting it to be 10. Anyone for help. Thanks in Advance. :) (5 Replies)
Discussion started by: paliwal
5 Replies

8. Shell Programming and Scripting

Global Variable

Hi, I have created a variable say today at the begin having 123 as its value and inside a for loop it gets resolved to some value say 150 in its first iteration. How can I use this value 150 ( 1st iteration's ) outside the scope of for loop ?. In the same way I wanted to use all iteration's... (1 Reply)
Discussion started by: penqueen
1 Replies

9. Shell Programming and Scripting

Question around Global Variable

Hi, I am using Linux and sh shell count=7 find * -prune -type d | sort -r -n | ( while read d; do if ; then echo "FOUND COUNTER1 is: $count" break 2; fi done echo "FOUND COUNTER2 is: $count" ) if ; then echo "Problem: Multiple or NO records...Please CHECK !!" fi Output: ... (4 Replies)
Discussion started by: mohtashims
4 Replies

10. Shell Programming and Scripting

[bash] why my variable is not updated?

Does anyone know why the below script is not working? Why is not the variable tot_files updated? location=$1 cd "$location" tot_files=0 ( echo "" # recursively gets the total number of files tot_files=$(for t in files ; do echo `find . -type ${t:0:1} | wc -l` $t | cut -f1... (12 Replies)
Discussion started by: soichiro
12 Replies
pthread_mutexattr_getprotocol(3C)										 pthread_mutexattr_getprotocol(3C)

NAME
pthread_mutexattr_getprotocol, pthread_mutexattr_setprotocol - get or set protocol attribute of mutex attribute object SYNOPSIS
cc -mt [ flag... ] file... -lpthread [ library... ] #include <pthread.h> int pthread_mutexattr_getprotocol(const pthread_mutexattr_t *restrict attr, int *restrict protocol); int pthread_mutexattr_setprotocol(pthread_mutexattr_t *attr, int protocol); The pthread_mutexattr_setprotocol() and pthread_mutexattr_getprotocol() functions, respectively, set and get the protocol attribute of a mutex attribute object pointed to by attr, which was previously created by the pthread_mutexattr_init() function. The protocol attribute defines the protocol to be followed in utilizing mutexes. The value of protocol may be one of PTHREAD_PRIO_NONE, PTHREAD_PRIO_INHERIT, or PTHREAD_PRIO_PROTECT, which are defined by the header <pthread.h>. When a thread owns a mutex with the PTHREAD_PRIO_NONE protocol attribute, its priority and scheduling are not affected by its mutex owner- ship. When a thread is blocking higher priority threads because of owning one or more mutexes with the PTHREAD_PRIO_INHERIT protocol attribute, it executes at the higher of its priority or the priority of the highest priority thread waiting on any of the mutexes owned by this thread and initialized with this protocol. When a thread owns one or more mutexes initialized with the PTHREAD_PRIO_PROTECT protocol, it executes at the higher of its priority or the highest of the priority ceilings of all the mutexes owned by this thread and initialized with this attribute, regardless of whether other threads are blocked on any of these mutexes. While a thread is holding a mutex that has been initialized with the PRIO_INHERIT or PRIO_PROTECT protocol attributes, it will not be sub- ject to being moved to the tail of the scheduling queue at its priority in the event that its original priority is changed, such as by a call to sched_setparam(). Likewise, when a thread unlocks a mutex that has been initialized with the PRIO_INHERIT or PRIO_PROTECT protocol attributes, it will not be subject to being moved to the tail of the scheduling queue at its priority in the event that its original prior- ity is changed. If a thread simultaneously owns several mutexes initialized with different protocols, it will execute at the highest of the priorities that it would have obtained by each of these protocols. When a thread makes a call to pthread_mutex_lock(), if the symbol _POSIX_THREAD_PRIO_INHERIT is defined and the mutex was initialized with the protocol attribute having the value PTHREAD_PRIO_INHERIT, when the calling thread is blocked because the mutex is owned by another thread, that owner thread will inherit the priority level of the calling thread as long as it continues to own the mutex. The implementa- tion updates its execution priority to the maximum of its assigned priority and all its inherited priorities. Furthermore, if this owner thread becomes blocked on another mutex, the same priority inheritance effect will be propagated to the other owner thread, in a recursive manner. If the symbol _POSIX_THREAD_PRIO_INHERIT is defined, when a mutex initialized with the protocol attribute having the value PTHREAD_PRIO_INHERIT dies, the behavior depends on the robustness attribute of the mutex. See pthread_mutexattr_getrobust_np(3C). A thread that uses mutexes initialized with the PTHREAD_PRIO_INHERIT or PTHREAD_PRIO_PROTECT protocol attribute values should have its con- tentionscope attribute equal to PTHREAD_SCOPE_SYSTEM (see pthread_attr_getscope(3C)) and its scheduling policy equal to SCHED_FIFO or SCHED_RR (see pthread_attr_getschedparam(3C) and pthread_getschedparam(3C)). If a thread with contentionscope attribute equal to PTHREAD_SCOPE_PROCESS and/or its scheduling policy equal to SCHED_OTHER uses a mutex initialized with the PTHREAD_PRIO_INHERIT or PTHREAD_PRIO_PROTECT protocol attribute value, the effect on the thread's scheduling and pri- ority is unspecified. The _POSIX_THREAD_PRIO_INHERIT and _POSIX_THREAD_PRIO_PROTECT options are designed to provide features to solve priority inversion due to mutexes. A priority inheritance or priority ceiling mutex is designed to minimize the dispatch latency of a high priority thread when a low priority thread is holding a mutex required by the high priority thread. This is a specific need for the realtime application domain. Threads created by realtime applications need to be such that their priorities can influence their access to system resources (CPU resources, at least), in competition with all threads running on the system. Upon successful completion, the pthread_mutexattr_getprotocol() and pthread_mutexattr_setprotocol() functions return 0. Otherwise, an error number is returned to indicate the error. The pthread_mutexattr_getprotocol() and pthread_mutexattr_setprotocol() functions will fail if: EINVAL The value specified by attr is NULL. ENOSYS Neither of the options _POSIX_THREAD_PRIO_PROTECT and _POSIX_THREAD_PRIO_INHERIT is defined and the system does not support the function. ENOTSUP The value specified by protocol is an unsupported value. The pthread_mutexattr_getprotocol() and pthread_mutexattr_setprotocol() functions may fail if: EINVAL The value specified by attr or protocol is invalid. EPERM The caller does not have the privilege to perform the operation. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Standard | +-----------------------------+-----------------------------+ |MT-Level |MT-Safe | +-----------------------------+-----------------------------+ pthread_create(3C), pthread_mutex_init(3C), pthread_cond_init(3C), pthread_mutexattr_getrobust_np(3C), attributes(5), standards(5) 23 Mar 2005 pthread_mutexattr_getprotocol(3C)
All times are GMT -4. The time now is 08:44 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy