Pthread_exit from a function called from a thread?

Of course. Otherwise what's the point of pthread_exit in the first place kernel.org/doc/man-pages/online/pages/ma... The pthread_exit() function shall terminate the calling thread.

Of course. Otherwise what's the point of pthread_exit in the first place. kernel.org/doc/man-pages/online/pages/ma... "The pthread_exit() function shall terminate the calling thread.

– George Kastrinis May 21 at 15:01 There have been complaints that the URL1 man pages are out of date. On a question like this it is probably irrelevant but a more authoritative source doesn't hurt. – Duck May 21 at 15:39 Oh thx.

I didn't know that. – George Kastrinis May 21 at 15:41 Yes, some of us (yours truly) are on a crusade to fix the die.net" rel="nofollow">die.net" rel="nofollow">die.net" rel="nofollow">die.net links that keep it at the top of SEO despite being full of outdated information. – R.. May 21 at 16:04.

From the documentation: The pthread_exit() function terminates the calling thread.

Yes, of course. It will also result in calling cleanup code, if any. Beware that it won't automatically clean application resources like mutexes etc.See pthread_exit() documentation for more information.

Except for robust mutexes - but using them for threads rather than processes would be rather wasteful. – R.. May 21 at 16:06.

Sure - thread context is unaffected by call/return. The thread IS calling pthread_exit(), no matter how long the call stack is. If 20 threads call foo then all 20 threads will exit.

Rgds, Martin.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.