ldv changed the topic of #strace to: https://strace.io | https://strace.io/logs/ | strace 5.2 is out | strace-devel@lists.strace.io for dev discussions
sscox has quit [Ping timeout: 245 seconds]
sscox has joined #strace
wladmis has quit [Quit: leaving]
wladmis has joined #strace
sscox has quit [Ping timeout: 276 seconds]
sscox has joined #strace
xse has joined #strace
sscox has quit [Ping timeout: 240 seconds]
<xse> Hello, any clue why my strace -f -c would close and display results while my strace -f hangs indefinitely ?
<xse> by indefinitely i mean for a few minutes as long as i care to not kill it
sscox has joined #strace
pombreda_ has joined #strace
pombreda_ has quit [Ping timeout: 240 seconds]
<ldv> xse: please be more specific
<ldv> in general, "strace -f" does more work than "strace -f -c"
pombreda_ has joined #strace
<xse> oh, my bad! in fact the program returned 1 on my console while leaving part of itself running somehow, it terminated the strace -c due to a syscall blocked by seccomp filter, strace working fine i was just confused by both results
wladmis has quit [Remote host closed the connection]
wladmis has joined #strace
sscox has quit [Ping timeout: 268 seconds]
sscox has joined #strace