pthread_create question

[douglaskbell]

What all is in 'pthread_t thread' after pthread_create( pthread_t *restrict thread, ... ); ??

Should 'thread' stay in scope after a thread is created?

That is, if a thread was created, 'thread' must stay in existence until the thread ends, right?

If 'thread' was defined in the function that called pthread_create,
but then the function returned while the thread was still running,
the data in 'thread' whould be on the stack, and vulnerable.

[white_hound]

You could receive all the information about pthread_create by inspecting the man pages ...
Anyhow, pay attention to 2 last arguments of pthread_create: function and argument. A new thread will be created, and this thread will execute the following code:

function( argument );
exit( 0 );

You see, when the thread function exits, the thread will exit - no magic. This has nothing to do with the future of a function that called pthread_create on the first place.
2 more things:
- the newly created thread and the creator thread will have common data section, i.e. common global variables area.
- when the main() function exits, all the threads that were created on its behalf, here or there, will exit.

NOTE:
All this (default) behavior may be re-configured on demand.

[douglaskbell]

Sorry, white_hound, but your reply had nothing to do with the original question.

I shall succinctly rephrase:
Does the data structure ‘thread’ which is the 1st argument of pthread_create(), need to remain in existence during the life of the thread, or is it just used by pthread_create() and not the thread.

To err on the side of caution, I assume the former and not the later.

I asked this because there is NOTHING about ‘thread’ in the man page of pthread_create().

[white_hound]

You are right, I didn't understand the pun: thread and 'thread' ...
No, there is no need to keep the thread structure.
All the essential structures are kept in the operating system kernel, and are not accessible to the user.

[douglaskbell]

Oh, okay. Thanks!