On Thu, Aug 14, 2014 at 07:17:48PM +0200, Toralf Förster wrote:
> With latest git tree I do get now a lot of lines like :
>
> [child0:1694] <timed out>
> [child0:1694] <timed out>
> [child0:1694] <timed out>
> [child1:1695] <timed out>
> [child0:1694] <timed out>
> [child0:1694] <timed out>
> [child1:1695] <timed out>
>
> for a command like this: MALLOC_CHECK_=2 trinity -C 2 -N 100000 -x mremap -q
> -V /tmp/victims/v1/v2
>
> It is intended ?
It's not a new thing (at least from Trinity's perspective).
If a syscall takes more than a second to complete, we send it a kill
signal. Some syscalls might be blocking on an fd though, and will
ignore those signals. You might try checking out /proc/1694/stack
and seeing where it's stuck. Much of the time it'll be doing sometihng
like a read() on a network socket. You could then exclude those
by specifiying just a specific network protocol with -P, or if you're
running current git, you can exclude sockets entirely with
--disable-fds=sockets
Dave
--
To unsubscribe from this list: send the line "unsubscribe trinity" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
