va_lists and threads

Felix Kater wrote:

The function f gets variable arguments and creates several threads

You'll probably get plenty of pointers that you are off-topic here.
The C language does not consider the possibility of multiple threads.

However, you are almost certainly looking to abuse the variable
arguments functionality. Read the language/library specification for
C89 (draft available free in pdf format online) and you see
stipulations such as "each invocation of va_start or va_arg shall be
matched by a corresponding invocation of va_end in the same function".
You also see that va_arg is defined as modifying the va_list object, so
sharing this is clearly unsafe.

Why not tell us a little more about what you are trying to do, and
we'll see whether we can help you achieve it in a robust manner, or
possibly we'll point you at a threads programming newsgroup.

Felix Kater wrote:

The function f gets variable arguments and creates several threads
which each shall receive all of the variable arguments. Like so:

void f(
my_callback* array_of_callbacks,
...){

va_list va;
va_start(va,array_of_callbacks);

/* now loop through array */

/* create thread for each callback
and pass va for each callback
*/

/* end of loop */

va_end va;

}

(1) Is it ok to use the locally created va and return from f() even
though the threads may still run and access va?

(2) Is it ok to va_start va *only once* for all callbacks/threads in the
loop or do I have to provide copies like va1, va2, va3 for each
iteration? This would make thinks complicated since the count is
variable: I would have to dynamically create an array of va -- who
would finalize them, however?

I think using a separate va_list object
for each callback would be fine.

--
aegis