After talking with Renzo Davoli we agreed that it makes most sense for
SYSCALL_ENTRY events to have engines' callbacks made in the reverse of the
normal order (FIFO vs LIFO). This ordering makes it sensical to have
nesting mutators and examiners as different utrace engines all watching
syscall
On 04/16, Roland McGrath wrote:
OK. For the moment, please forget about these changes. Let's recall
do_wait() has the ancient bug. wait_task_zombie() sets EXIT_DEAD
unconditionally, then drops tasklist. If we are not the real_parent
and the child was traced, we may restore exit_state =
Renzo and I met at the conference in San Francisco last week and spoke more
about his use case. He showed me a fine demo live of what his cool hacks
can do, and a clear demonstration of the nesting issue. Rather than
responding point by point, I'll follow up momentarily on the API change I'm
