1 <h2>task_set_emulation_vector
</h2>
4 <strong>Function
</strong> - Establish the target task's user-level system call handlers.
7 <strong>kern_return_t task_set_emulation_vector
</strong>
8 <strong>(task_t
</strong> <var>task
</var>,
9 <strong>int
</strong> <var>vector_start
</var>,
10 <strong>emulation_vector_t
</strong> <var>emulation_vector
</var>,
11 <strong>mach_msg_type_number_t
</strong> <var>emulation_vector_count
</var><strong>);
</strong>
19 The port for the task for which to establish the
22 <dt> <var>vector_start
</var>
25 The syscall number corresponding to the first element of
26 <var>emulation_vector
</var>.
28 <dt> <var>emulation_vector
</var>
30 [pointer to in array of
<strong>vm_address_t
</strong>]
31 An array of routine entrypoints
32 for the system calls starting with syscall number
<var>vector_start
</var>.
34 <dt> <var>emulation_vector_count
</var>
37 The number of elements in
<var>emulation_vector
</var>.
41 The
<strong>task_set_emulation_vector
</strong> function establishes
42 a handler within the task
43 for a set of system calls. When a thread executes a system call
45 numbers, the system call will be redirected to the corresponding
47 the task's address space.
49 These emulation handler addresses are inherited by child processes.
52 This interface is machine word length specific because of the
54 in the
<var>emulation_vector
</var> parameter.
55 <h3>RETURN VALUES
</h3>
57 Only generic errors apply.
58 <h3>RELATED INFORMATION
</h3>
61 <a href=
"task_get_emulation_vector.html"><strong>task_get_emulation_vector
</strong></a>.