Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

_lwp_makecontext(3) [netbsd man page]

_LWP_MAKECONTEXT(3)					   BSD Library Functions Manual 				       _LWP_MAKECONTEXT(3)

_lwp_makecontext -- create a new initial light-weight process execution context LIBRARY
Standard C Library (libc, -lc) SYNOPSIS
#include <lwp.h> void _lwp_makecontext(ucontext_t *context, void (*start_routine)(void *), void *arg, void *private, caddr_t stack_base, size_t stack_size); DESCRIPTION
_lwp_makecontext() initializes the context structure pointed to by context in a manner suitable for using with _lwp_create(2). The LWP will begin execution at the function specified by start_routine which will be passed a single argument arg. The LWP private data pointer will be set to private. The stack region for the new LWP is specified by the stack_base and stack_size arguments. The signal mask in the context structure is not initialized by _lwp_makecontext(). SEE ALSO
_lwp_create(2), _lwp_getprivate(2) HISTORY
The _lwp_create() system call first appeared in NetBSD 2.0. BUGS
The LWP private data pointer is not initialized by the current implementation of _lwp_makecontext(). BSD
January 16, 2003 BSD

Check Out this Related Man Page

_LWP_KILL(2)						      BSD System Calls Manual						      _LWP_KILL(2)

_lwp_kill -- send a signal to a light-weight process LIBRARY
Standard C Library (libc, -lc) SYNOPSIS
#include <lwp.h> int _lwp_kill(lwpid_t lwp, int sig); DESCRIPTION
_lwp_kill() sends the signal specified by sig to the light-weight process specified by lwp. If the sig argument is given as 0 (zero), _lwp_kill will test for the existence of the target LWP, but will take no further action. Job control signals and uncatchable signals can not be directed to a specific LWP: if posted with _lwp_kill, they will affect all LWPs in the process. Signals will be posted successfully to suspended LWPs, but will not be handled further until the LWP has been continued. RETURN VALUES
A 0 value indicates that the call succeeded. A -1 return value indicates an error occurred and errno is set to indicate the reason. ERRORS
[EINVAL] sig is not a valid signal number. [ESRCH] No LWP can be found in the current process corresponding to that specified by lwp. SEE ALSO
_lwp_continue(2), _lwp_suspend(2), kill(2), sigaction(2), signal(7) HISTORY
The _lwp_kill() system call first appeared in NetBSD 5.0. BSD
January 20, 2007 BSD
Man Page