> On 11/18, Roland McGrath wrote:
> >
> > > In any case, what is the rationality?
> >
> > The rationale is that if you see utrace_resume_action(action)==UTRACE_STOP
> > in your callback, then you know another engine asked for stop
>
> Yes, but engine can't know if the next one is going to return
>
On 11/18, Roland McGrath wrote:
>
> > In any case, what is the rationality?
>
> The rationale is that if you see utrace_resume_action(action)==UTRACE_STOP
> in your callback, then you know another engine asked for stop
Yes, but engine can't know if the next one is going to return
UTRACE_STOP.
> a
> Just can't understand UTRACE_SYSCALL_RESUMED code.
You understand too well! :-)
> To the pointed, I tried to read the docs:
>
> * When %UTRACE_STOP is used in @report_syscall_entry, then @task
> * stops before attempting the system call. In this case, another
> * @report_sys
Just can't understand UTRACE_SYSCALL_RESUMED code.
To the pointed, I tried to read the docs:
* When %UTRACE_STOP is used in @report_syscall_entry, then @task
* stops before attempting the system call. In this case, another
* @report_syscall_entry callback follows after @t
