[src/trunk]: src/share/man/man3 Continue the discussion w.r.t. SIGEV_THREAD b...

[jruoho <jruoho%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/341b512e864c
branches:  trunk
changeset: 754996:341b512e864c
user:      jruoho <jruoho%NetBSD.org@localhost>
date:      Wed May 19 08:02:46 2010 +0000

description:
Continue the discussion w.r.t. SIGEV_THREAD by nothing that pthread_join(3)
should be out of the question and that thread stack cannot be recovered.

diffstat:

 share/man/man3/sigevent.3 |  19 ++++++++++++++++++-
 1 files changed, 18 insertions(+), 1 deletions(-)

diffs (33 lines):

diff -r d10a94b2e6f4 -r 341b512e864c share/man/man3/sigevent.3
--- a/share/man/man3/sigevent.3 Wed May 19 06:59:44 2010 +0000
+++ b/share/man/man3/sigevent.3 Wed May 19 08:02:46 2010 +0000
@@ -1,4 +1,4 @@
-.\" $NetBSD: sigevent.3,v 1.2 2010/05/19 06:59:44 wiz Exp $
+.\" $NetBSD: sigevent.3,v 1.3 2010/05/19 08:02:46 jruoho Exp $
 .\"
 .\" Copyright (c) 2010 Jukka Ruohonen <jruohonen%iki.fi@localhost>
 .\"
@@ -141,6 +141,23 @@
 the type is
 .Va pthread_attr_t
 in practice.)
+.Pp
+The threads are created as detached,
+or in an unspecified way if
+.Xr pthread_attr_setdetachstate 3
+is used with
+.Va sigev_notify_attributes
+to set
+.Dv PTHREAD_CREATE_JOINABLE .
+It is not valid to call
+.Xr pthread_join 3
+in either case.
+Hence, it is also impossible to determine the lifetime of the created thread.
+This in turn means that it is neither possibly to recovery the memory nor
+the address of the memory possibly dedicated as thread stack via
+.Fn pthread_attr_setstack
+or
+.Fn pthread_attr_setstackaddr .
 .El
 .\"
 .\" .Sh EXAMPLES