On 10/19, Roland McGrath wrote:
But that's how it used to be, and then we changed it.
So it merits digging up our old discussion threads that led to doing that
and see what all we had in mind then.
I tried to grep my mail archives and google, but failed to find anything
related.
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
On 09/23, Roland McGrath wrote:
OK, finish_callback_report() and utrace_control(DETACH) can set
TIF_NOTIFY_RESUME.
Right. Those utrace_resume has the report.action==UTRACE_RESUME bail-out
case. So either that would change or detach would also do UTRACE_REPORT.
But what if there are no
