POSIX threads and data safety Post: 302293906

7 More Discussions You Might Find Interesting

1. Programming

select/poll and Signal Safety

Hi I am struggling to understand why one should use pselect()/ppoll() instead of wrapping an ordinary select() or poll() call around sigprocmask(). The linux man page talks about �race conditions�, but how would such dangers occur? I plan to use poll() for an application (since ppoll() isn't...

2. Programming

POSIX threads

Hello ! Let's supose I have a main function in C , and two POSIX threads. I give you an example down : int main() { int something; char else; void *FirstThread(); void *SecondThread(); .. <start those two pthreads ..> return 0;} void *FirstThread() { ... } void *SecondThread()...

3. UNIX for Advanced & Expert Users

Threads and Threads Count ?

Hi all, How can I get the list of all Threads and the Total count of threads under a particular process ? Do suggest !! Awaiting for the replies !! Thanks Varun:b:

4. UNIX for Advanced & Expert Users

Posix threads

Hi, consider the code below: #include <stdio.h> . . struct myStruct { char *message ; int id; }; . . . void *thread_function( void *ptr ); nt main() { pthread_t thread1, thread2 ,thread3 ; struct myStruct nico1;

5. Programming

need help with posix threads

Hi, I am new to posix threads. The no of threads to be created depends on the runtime. If I get the number of threads, I need to forward declare pthread_t mythread; how to do that can I use pointers and use malloc()?? I also have another question. The pthread_join is used to make...

6. UNIX for Advanced & Expert Users

Linkage of POSIX threads function calls

I wonder if someone knows what is the rationale behind linking function calls of the POSIX threads library at link-time vs. run-time. For example, if I create the following program: #include <pthread.h> void noop() { return; } int main() { pthread_self(); pthread_atfork(noop,...

7. Solaris

SUNFIRE V240 procedure to shutdown with safety in order to replace power cables

Question: Which commands to use to shutdown with safety the server;

LEARN ABOUT X11R4

xinitthreads

XInitThreads(3) 						  XLIB FUNCTIONS						   XInitThreads(3)

NAME

       XInitThreads, XLockDisplay, XUnlockDisplay - multi-threading support

SYNTAX

       Status XInitThreads(void);

       void XLockDisplay(Display *display);

       void XUnlockDisplay(Display *display);

ARGUMENTS

       display	 Specifies the connection to the X server.

DESCRIPTION

       The XInitThreads function initializes Xlib support for concurrent threads.  This function must be the first Xlib function a multi-threaded
       program calls, and it must complete before any other Xlib call is made.	This function returns a nonzero status if initialization was suc-
       cessful; otherwise, it returns zero.  On systems that do not support threads, this function always returns zero.

       It is only necessary to call this function if multiple threads might use Xlib concurrently.  If all calls to Xlib functions are protected
       by some other access mechanism (for example, a mutual exclusion lock in a toolkit or through explicit client programming), Xlib thread ini-
       tialization is not required.  It is recommended that single-threaded programs not call this function.

       The XLockDisplay function locks out all other threads from using the specified display.	Other threads attempting to use the display will
       block until the display is unlocked by this thread.  Nested calls to XLockDisplay work correctly; the display will not actually be unlocked
       until XUnlockDisplay has been called the same number of times as XLockDisplay.  This function has no effect unless Xlib was successfully
       initialized for threads using XInitThreads.

       The XUnlockDisplay function allows other threads to use the specified display again.  Any threads that have blocked on the display are
       allowed to continue.  Nested locking works correctly; if XLockDisplay has been called multiple times by a thread, then XUnlockDisplay must
       be called an equal number of times before the display is actually unlocked.  This function has no effect unless Xlib was successfully ini-
       tialized for threads using XInitThreads.

SEE ALSO

       Xlib - C Language X Interface

X Version 11							   libX11 1.2.1 						   XInitThreads(3)