1 <h2>receive_samples
</h2>
3 Server Interface - Handles the occurrence of a PC sampling message
7 <strong>kern_return_t receive_samples
</strong>
8 <strong>(mach_port_t
</strong> <var>sample_port
</var>,
9 <strong>sample_array_t
</strong> <var>samples
</var>,
10 <strong>mach_msg_type_number_t
</strong> <var>sample_count
</var><strong>);
</strong>
14 <dt> <var>sample_port
</var>
16 [in sample (receive) right] The port to which the sample message was
19 <dt> <var>samples
</var>
21 [pointer to in array of vm_address_t] An array of PC sample values.
23 <dt> <var>sample_count
</var>
25 [in scalar] The number of values in samples.
30 A
<strong>receive_samples
</strong> function is called by
31 <strong>prof_server
</strong> as the result of a kernel
32 message indicating that a set of program counter samples has been gathered.
33 The parameter
<var>sample_port
</var> specifies the port named via
34 a previous call to
<strong>task_sample
</strong>
35 or
<strong>thread_sample
</strong>.
39 This interface is machine word length specific because of the virtual addresses
40 in the
<var>samples
</var> parameter.
46 <h3>RELATED INFORMATION
</h3>
49 <a href=
"task_sample.html"><strong>task_sample
</strong></a>,
50 <a href=
"thread_sample.html"><strong>thread_sample
</strong></a>,
51 <a href=
"prof_server.html"><strong>prof_server
</strong></a>.