aboutsummaryrefslogtreecommitdiffstats
path: root/man3/getcontext.3
diff options
context:
space:
mode:
Diffstat (limited to 'man3/getcontext.3')
-rw-r--r--man3/getcontext.314
1 files changed, 7 insertions, 7 deletions
diff --git a/man3/getcontext.3 b/man3/getcontext.3
index 6af4da8664..0a9981a84c 100644
--- a/man3/getcontext.3
+++ b/man3/getcontext.3
@@ -46,7 +46,7 @@ and
.BR swapcontext (3)
that allow user-level context switching between multiple
threads of control within a process.
-.LP
+.PP
The
.I mcontext_t
type is machine-dependent and opaque.
@@ -91,14 +91,14 @@ and
is the
machine-specific representation of the saved context,
that includes the calling thread's machine registers.
-.LP
+.PP
The function
.BR getcontext ()
initializes the structure
pointed at by
.I ucp
to the currently active context.
-.LP
+.PP
The function
.BR setcontext ()
restores the user context
@@ -111,11 +111,11 @@ or
.BR makecontext (3),
or passed as third argument to a signal
handler.
-.LP
+.PP
If the context was obtained by a call of
.BR getcontext (),
program execution continues as if this call just returned.
-.LP
+.PP
If the context was obtained by a call of
.BR makecontext (3),
program execution continues by a call to the function
@@ -132,7 +132,7 @@ specified as the
first argument of that call to
.BR makecontext (3).
When this member is NULL, the thread exits.
-.LP
+.PP
If the context was obtained by a call to a signal handler,
then old standard text says that "program execution continues with the
program instruction following the instruction interrupted
@@ -186,7 +186,7 @@ is from the first call, or via a
call.
The user has to invent her own bookkeeping device, and a register
variable won't do since registers are restored.
-.LP
+.PP
When a signal occurs, the current user context is saved and
a new context is created by the kernel for the signal handler.
Do not leave the handler using