Sorry for late reply.
I delayed it because I hoped I will see how to solve this problem
cleanly during the rewrite.
No. I don't see how we can fix this without some changes in utrace.
Just in case, let me remind you what is the problem. For simplicity,
let's ignore SIGKILL issues, and let's
I'll point out that the only symptom that matters to ptrace is -exit_code
and that issue disappears if you stop overloading it for ptrace purposes,
which is the clean thing to do in the long run anyway. But there are
subtler issues that haven't yet directly affected ptrace.
In this scenario, the
I seem to find the problem, and I do not see a simple solution.
Will try to think more tomorrow with a fresh head, but perhaps
you can help. looks like we need some changes in utrace/signal
layer.
Suppose that a tracee is going to report, say, PTRACE_EVENT_FORK.
The callback returns UTRACE_STOP.
