<timed out>
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 ?
Signature · 1 line
Toralf
Quoted 10 lines · Toralf Förster
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>
Quoted 3 lines
for a command like this: MALLOC_CHECK_=2 trinity -C 2 -N 100000 -x mremap -q -V
/tmp/victims/v1/v2It 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
Quoted 25 lines · Dave Jones
Quoted 10 lines · Toralf Förster
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>Quoted 3 lines
for a command like this: MALLOC_CHECK_=2 trinity -C 2 -N 100000 -x mremap -q -V
/tmp/victims/v1/v2It 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/stackand seeing where it's stuck. Much of the time it'll be doing sometihng like aread()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
Quoted 3 lines
Dave
/me wonders if dfdb9560d brought this message to my eyes ?
Well for the stack trace feature I've to wait till it is implemented - Richard Weinberger told me that there#S a guy just doing it.
But thx for the "--disable-fds=sockets" hint - will play with it.
Signature · 1 line
Toralf
Quoted 5 lines · Toralf Förster
Quoted 4 lines
Quoted 3 lines
With latest git tree I do get now a lot of lines like :
[child0:1694] <timed out>
/me wonders if
dfdb9560dbrought this message to my eyes ?
ah, yes, quite likely. I need to go over a lot of that loglevel code again at some point, there are a few problems with it. Kinda low down on my list right now, but I'll get to it before the next tarball release.
Quoted 1 line
Well for the stack trace feature I've to wait till it is implemented - Richard Weinberger told me that there#S a guy just doing it.
Bah, I thought this was ubiquitous by now..
Dave