> > This model seems like a better fit for ptrace to me. The anchoring data
> > structure is the tracer's tracees list, which links together the
> > ptrace_context structs. A live ptrace_context has an engine pointer and
> > a ref for it.
>
> OK. Not that I really understand this all in details,
> > I don't really understand why the SIGSTOP is your concern.
> > No matter what, you send that last, after ptrace is wired up to catch it.
>
> Because the tracee must not dequeue and handle this SIGSTOP until it sees
> UTRACE_EVENT_SIGNAL_ALL in ->utrace_flags.
Right. utrace_set_events() sets
Trying to understand what ptrace_report_signal() should do, a couple
of questions...
Why does utrace_signal_handler() set ->signal_handler when !stepping?
If I understand correctly, the logic is
if (stepping)
make sure that before return to user-space
UTR
