pthread: one printf statement get printed twice in child thread

by

Threading generally occurs by time-division multiplexing. It is generally in-efficient for the processor to switch evenly between two threads, as this requires more effort and higher context switching. Typically what you’ll find is a thread will execute several times before switching (as is the case with examples 3 and 4. The child thread executes more than once before it is finally terminated (because the main thread exited).

Example 2: I don’t know why x is increased by the child thread while there is no output.

Consider this. Main thread executes. it calls the pthread and a new thread is created.The new child thread increments x. Before the child thread is able to complete the printf statement the main thread kicks in. All of a sudden it also increments x. The main thread is however also able to run the printf statement. Suddenly x is now equal to 3.
The main thread now terminates (also causing the child 3 to exit).
This is likely what happened in your case for example 2.

Examples 3 clearly shows that the variable x has been corrupted due to inefficient locking and stack data corruption!!

For more info on what a thread is.

Link 1 – Additional info about threading

Link 2 – Additional info about threading

Also what you’ll find is that because you are using the global variable of x, access to this variable is shared amongst the threads. This is bad.. VERY VERY bad as threads accessing the same variable create race conditions and data corruption due to multiple read writes occurring on the same register for the variable x.
It is for this reason that mutexes are used which essentially create a lock whilst variables are being updated to prevent multiple threads attempting to modify the same variable at the same time.
Mutex locks will ensure that x is updated sequentially and not sporadically as in your case.

See this link for more about Pthreads in General and Mutex locking examples.
Pthreads and Mutex variables

Cheers,
Peter

More Related Contents:

  1. cmake and libpthread
  2. C: unable to print from file
  3. printf anomaly after “fork()”
  4. How do you allow spaces to be entered using scanf?
  5. Python’s many ways of string formatting — are the older ones (going to be) deprecated?
  6. C/C++ printf() before scanf() issue
  7. Set variable text column width in printf
  8. printf with std::string?
  9. Printing 1 to 1000 without loop or conditionals
  10. How to printf a memory address in C
  11. when g++ static link pthread, cause Segmentation fault, why?
  12. string format for intptr_t and uintptr_t
  13. Is it OK to call pthread_exit from main?
  14. Why doesn’t scanf need an ampersand for strings and also works fine in printf (in C)?
  15. How do I print a non-null-terminated string using printf?
  16. Strings and character with printf
  17. How to repeat a char using printf?
  18. C++ equivalent of sprintf?
  19. C Programming: Forward variable argument list
  20. Correct printf format specifier for size_t: %zu or %Iu?
  21. Left-pad printf with spaces
  22. Using C/Pthreads: do shared variables need to be volatile?
  23. Scanf/Printf double variable C
  24. Is accept() thread-safe?
  25. Printing chars and their ASCII-code in C
  26. Do pthread mutexes work across threads if in shared memory?
  27. C printf using %d and %f
  28. printf() with no arguments in C compiles fine. how?
  29. Why doesn’t sprintf() output anything?
  30. OpenSSL and multi-threads

Leave a Comment