I do not know what to do with ptrace_detach()-wake_up_process().
It and ptrace_resume()-wake_up_process() are both clearly wrong in
general. I think all we really need to worry about is making sure that the
ptrace-tests suite has tests that express all the assumptions and
requirements of
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
UTRACE_SIGNAL_HANDLER will be reported.
This is understandable. More or
Another question. How can -report_signal(info) change info-si_signo
(or other data in *info) when we have multiple engines? I mean, how
can engines cooperate if they want to change -si_signo.
This is just an instance of the general subject of engine cooperation when
engines do perturbation.
