Lines Matching refs:call

44 only a single function call, transferring control back to the point at
50 environment in which the call to @code{setjmp} appears in an object of
52 the call to @code{setjmp}, but if an exit is later made to this return
56 between an ordinary return and a return made by a call to
72 @code{setjmp}.  A normal call to @code{setjmp} returns zero, so the
75 @code{do_command}, then it actually appears as if the @emph{same} call
111 @c   __sigjmp_save(!savemask) ok, does not call sigprocmask
135 @var{state}, and continues execution from the call to @code{setjmp} that
184 function containing the @code{setjmp} call that have been changed since
185 the call to @code{setjmp} are indeterminate, unless you have declared
230 argument.  If the @code{sigsetjmp} call that set this @var{state} used a
289 @c syscall.  A few cases call the sigprocmask function, but that's safe
295 @code{getcontext} call just returned.
324 initialized by a call to @code{getcontext}.  The context will be
328 @var{argc} parameter in the call to @code{makecontext}.
330 Before the call to this function the @code{uc_stack} and @code{uc_link}
383 @code{getcontext} call just returned.
385 If the context was modified with a call to @code{makecontext} execution
390 time of the call.  If @code{uc_link} was a null pointer the application
394 If the context was created by a call to a signal handler or from any
412 @c Linux-only implementations mostly in assembly.  Some ports call or
418 in the object pointed to by @var{oucp} as if this was a call to
419 @code{getcontext}.  The saved context would resume after the call to
482 to call every once in a while @code{swapcontext} to continue running a