1<h2>task_get_emulation_vector</h2> 2<hr> 3<p> 4<strong>Function</strong> - Return an array identifying the target task's user-level system call handlers. 5<h3>SYNOPSIS</h3> 6<pre> 7<strong>kern_return_t task_get_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> 12</pre> 13<h3>PARAMETERS</h3> 14<dl> 15<p> 16<dt> <var>task</var> 17<dd> 18[in task send right] 19The port for the task for which the system call 20handler addresses are desired. 21<p> 22<dt> <var>vector_start</var> 23<dd> 24[out scalar] 25The syscall number corresponding to the first element of 26<var>emulation_vector</var>. 27<p> 28<dt> <var>emulation_vector</var> 29<dd> 30[out pointer to dynamic array of <strong>vm_address_t</strong>] 31Pointer to the returned 32array of routine entrypoints for the system calls starting with syscall 33number <var>vector_start</var>. 34<p> 35<dt> <var>emulation_vector_count</var> 36<dd> 37[out scalar] 38The number of entries filled by the kernel. 39</dl> 40<h3>DESCRIPTION</h3> 41<p> 42The <strong>task_get_emulation_vector</strong> function returns the 43user-level syscall handler entrypoint addresses. 44<h3>NOTES</h3> 45<p> 46This interface is machine word length specific because of the 47virtual addresses in the <var>emulation_vector</var> parameter. 48<h3>RETURN VALUES</h3> 49<p> 50Only generic errors apply. 51<h3>RELATED INFORMATION</h3> 52<p> 53Functions: 54<a href="task_set_emulation_vector.html"><strong>task_set_emulation_vector</strong></a>. 55