It's essentially the same as an interrupt handler - your entire address 
space is mapped, but you are limited in stack usage
and can't make any kernel calls.

On 12-02-24 5:59 AM, Konstantin V wrote:
> Hello QNX Developers,
>
> As I understand from docs, I can attach event handling routine via  TraceEvent (_NTO_TRACE_ADDEVENTHANDLER, ...) and 
it will be called by the kernel directly.
>
> 1) What are the stack restrictions ?
>
> 2) How much of process address space is mapped ?
>      Can I affect it in any way ?
>      Example code from QNX documentation accesses process global variable, so I assume that at least
>      some part of process address space is mapped.
>      In case of complete address space is mapped, then may be it makes
>      sense to keep the size of the executable implementing dynamic kernel event filtering
>      as small as possible...
>
> Thank you!
>
>
>
>
> _______________________________________________
>
> OSTech
> http://community.qnx.com/sf/go/post91764
>

-- 
cburgess@qnx.com