On 10/14, Roland McGrath wrote:
In short: I no longer understand why utrace-resume can be UTRACE_*STEP
when the tracee is stopped, and in fact I think this is not right.
I think we didn't have that originally.
Yes.
The rationale that I remember is
the idea that you should be able to
Probably, I am not sure. I can't recall the previous discussions.
Me either (except hazily the one notion I mentioned), but that's why
we have mailing list archives.
Afaics, this was introduced by 26fefca955cc7c3c83014be2e10b773209d32eea
utrace: sticky resume action. Before that patch the
Yes. But, with this patch, in this case
utrace_barrier()-get_utrace_lock(attached = false) returns success
and then we check utrace-reporting == engine.
I guess that's OK if -reporting == engine is always set when any kind of
callback might be in progress.
(Hmm. Probably utrace-reap = T case
