On 09/23, Roland McGrath wrote: > > > Hmm. Not sure how to fix this... > > Well, one thing it can do is just punt them down to UTRACE_REPORT. > It's only a non-guaranteed optimization that these effects happen > directly from utrace_control() without being reinforced by a final > report_quiesce/report_signal callback, after all.
Yes, agreed. And. If we have multiple tracers, then utrace_control(SINGLESTEP) just "fools" the caller, another engine can do utrace_control(RESUME) at any moment. I think you are right, utrace_control() should simply consider UTRACE_XXXSTEP as UTRACE_REPORT. Oleg.
