On Tue, Jan 24, 2017 at 03:32:25PM +0100, Hrvoje Popovski wrote: > Hi all, > > every time when quitting tcpdump with ^C i see that log on console. > Source is fetched few minutes ago ... > > Don't know is this good or bad so i'm sending it here .. > > tcpdump(63969): syscall 54 "tty" > tcpdump(87912): syscall 54 "tty" > tcpdump(35062): syscall 54 "tty" > tcpdump(68817): syscall 54 "tty" >
it is error related to pledge(2). could you run tcpdump with ktrace -di, and interrupt it quickly with ^C ? # ktrace -di tcpdump ... A gdb backtrace is also welcome :) The purpose is to check: - what are the pledge promises: 96021 tcpdump CALL pledge(0x34a0d6f4,0) 96021 tcpdump STRU pledge request="stdio rpath inet unix dns recvfd bpf" 96021 tcpdump RET pledge 0 ... 29420 tcpdump CALL pledge(0x34a0d169,0) 29420 tcpdump STRU pledge request="stdio" 29420 tcpdump RET pledge 0 - what are the argument passed to ioctl(2) which case pledge failure. 939 tcpdump CALL ioctl(4,TIOCSPGRP,0xcf7e2824) 939 tcpdump PLDG ioctl, "tty", errno 1 Operation not permitted 939 tcpdump PSIG SIGABRT SIG_DFL 939 tcpdump NAMI "tcpdump.core" (here is a error I faked as I don't reproduce your problem). Thanks. -- Sebastien Marie
