UTRACE_STOP race condition?

[Frank Ch. Eigler]

Renzo Davoli <renzo at cs.unibo.it> writes:

> [...]
> If the report function returns UTRACE_STOP the traced process stays in a
> quiescent state and the module wakes it up by a 
> utrace_control(...,UTRACE_RESUME) call *later*.
> [...]
> If the module wakes the traced process too quickly, utrace has not yet put
> it into a "stopped" state, therefore UTRACE_RESUME gets lost.
> [...]
> The module has "decided" UTRACE_STOP at t=1, then the module can call
> utrace_control(...,UTRACE_RESUME) at any t>1. [...]

This may not answer your question, but I believe it is not proper to
to make this call at any time t>1, only once you receive the quiesce
callback.


- FChE