Take care that the manpage of pthread_mutex_destroy says:
"Attempting to destroy a locked mutex, or ...., results in undefined behavior."
But this is what the code is doing in threadpool_free().

Hello,
I tried doing a make from the root directory of threadpool-master, but it gives me make errors as follows. I'm surprised because the files contain #include pthread.h and the Makefile contains -lpthread as well. How can I get it to build?

cc -lpthread tests/thrdtest.o src/threadpool.o -o tests/thrdtest src/threadpool.o: In function threadpool_create: threadpool.c:(.text+0x146): undefined reference to pthread_create src/threadpool.o: In function threadpool_destroy: threadpool.c:(.text+0x3c1): undefined reference to pthread_join collect2: ld returned 1 exit status make: *** [tests/thrdtest] Error 1

Say we create 20 threads with threadpool_create() and call threadpool_add() to add a task into the task queue right away.
Is there possibility that a creating thread (in threadpool_thread()) called pthread_mutex_lock() at line 273 right after threadpool_add() called pthread_cond_signal() at line 186 so that the creating thread acquires the lock before the thread to be woken and in turn, making the pool->count a negative number?

Hi,

I've just tried this thread pool and it seems to work pretty well. However, I was wondering if there is a way to wait for all threads to finish without actually freeing the memory (so that the pool is still usable).

I'm implementing a method that performs several sequential analyses (where each depends on the result of the previous) and, since it is a bit slow, I'd like to thread each analysis. So, ideally, I'd create the thread pool in the beginning, launch all tasks for the first analysis and wait for all tasks to finish. Then, I'd process the results and launch the jobs of the next analysis (and so on). Is it possible?

Where implements "Reserves one task for signaling the queue is full."?
I can't found it.
Is it unnecessary?