Re: Why return probes of some syscalls sometimes are not called?

On Thu, 9 Mar 2017 15:01:38 +0000 (UTC)
Mathieu Desnoyers <[email protected]> wrote:

 
> Another more likely scenario is if a multithreaded process
> has many threads blocked (e.g. on a futex), and one of the threads
> exits cleanly or forks. I suspect the kernel will just tear down the
> other threads without hitting syscall exit.

Maybe, if this happens multiple times, it could cause those kinds of
numbers. A fork was done zero times according to the numbers. Maybe
exit should be measured too.

-- Steve