Unexpected output in a multithreaded program

by

As highlighted by @R.. in the comments, this appears to be a bug in the implementation of glibc (assuming you are using Linux — I can reproduce this on Linux 2.17 compiled with GCC 4.9.1), in that exit() doesn’t ensure, while flushing and closing streams, there’s no race when it’s called by one thread when multiple threads use stdout.

The following from flockfile manual clearly indicates that the behaviour observed is not correct:

The stdio functions are thread-safe. This is achieved by
assigning to each FILE object a lockcount and (if the lockcount is
nonzero) an owning thread. For each library call, these functions
wait until the FILE object is no longer locked by a different
thread, then lock it, do the requested I/O, and unlock the object
again.

In light of this, the following options can be considered as a workaround (as there’s no response to the bug report) to this particular case that we observed here.

Both the threads “share” the stdout stream and I think, the “extra” output is printed because of the premature exit of main thread.

printf buffers (in sample_thread()) the output and before it could clear it’s buffer (due to \n in printfs), main thread exits. Hence forcing the flush of stdout buffer when the process exits.

To fix,

1) you could call setbuf() in main() before creating the thread:

setbuf(stdout, NULL);

to not buffer stdout at all.

Or
2) call pthread_exit() in both threads so that the process continues if either thread dies.

Or
3) call pthread_join() in main thread so that main thread waits for the completion of sample_thread thread.

Either one of these will avoid the issue.

More Related Contents:

  1. Undefined reference to pthread_create in Linux
  2. When the main thread exits, do other threads also exit?
  3. Kill Thread in Pthread Library
  4. Is it possible to determine the thread holding a mutex?
  5. Can I get Unix’s pthread.h to compile in Windows?
  6. Pthread Run a thread right after it’s creation
  7. How do you query a pthread to see if it is still running?
  8. Using C/Pthreads: do shared variables need to be volatile?
  9. Linux/POSIX equivalent for Win32’s CreateEvent, SetEvent, WaitForSingleObject
  10. Which thread handles the signal?
  11. Is atoi multithread safe? [closed]
  12. Still Reachable Leak detected by Valgrind
  13. Is errno thread-safe?
  14. POSIX threads and signals
  15. How do I start threads in plain C?
  16. Multiple arguments to function called by pthread_create()?
  17. Wake up thread blocked on accept() call
  18. Undefined reference to ‘pthread_create’ — linker command option order (libraries before/after object files?) [duplicate]
  19. Signal handling with multiple threads in Linux
  20. POSIX API call to list all the pthreads running in a process
  21. How to set the stacksize with C++11 std::thread
  22. How to signal select() to return immediately?
  23. Interprocess mutex with pthreads
  24. Does any C library implement C11 threads for GNU/Linux?
  25. When to use pthread condition variables?
  26. Is accept() thread-safe?
  27. Is it possible to access/update the child thread’s resource from parent thread?
  28. How to set up pthreads on windows?
  29. C++11 std::threads vs posix threads
  30. WaitForSingleObject and WaitForMultipleObjects equivalent in Linux?

Leave a Comment