From owner-freebsd-hackers@FreeBSD.ORG Thu Oct 11 11:49:44 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0F75F5F1 for ; Thu, 11 Oct 2012 11:49:44 +0000 (UTC) (envelope-from kwiat3k@panic.pl) Received: from mail.panic.pl (mail.panic.pl [188.116.33.105]) by mx1.freebsd.org (Postfix) with ESMTP id BB66E8FC14 for ; Thu, 11 Oct 2012 11:49:43 +0000 (UTC) Received: from mail.panic.pl (unknown [188.116.33.105]) by mail.panic.pl (Postfix) with ESMTP id 73C789B794 for ; Thu, 11 Oct 2012 13:40:56 +0200 (CEST) X-Virus-Scanned: amavisd-new at panic.pl Received: from mail.panic.pl ([188.116.33.105]) by mail.panic.pl (mail.panic.pl [188.116.33.105]) (amavisd-new, port 10024) with ESMTP id vx+vnmdr1cJG for ; Thu, 11 Oct 2012 13:40:56 +0200 (CEST) Received: from localhost.localdomain (admin.wp-sa.pl [212.77.105.137]) by mail.panic.pl (Postfix) with ESMTPSA id 1E64A9B78D for ; Thu, 11 Oct 2012 13:40:56 +0200 (CEST) Date: Thu, 11 Oct 2012 13:41:08 +0200 From: Mateusz Kwiatkowski To: freebsd-hackers@freebsd.org Subject: truss kills process? Message-ID: <20121011134108.65fd11ba@panic.pl> Organization: Panic.PL X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.13; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2012 11:49:44 -0000 Hello, We noticed quite strange behaviour of truss: # sleep 100 & [1] 93212 # truss -p 93212 sigprocmask(SIG_BLOCK,SIGHUP|SIGINT|SIGQUIT|SIGKILL|SIGPIPE|SIGALRM|SIGTERM|SIGURG|SIGSTOP|SIGTSTP|SIGCONT|SIGCHLD|SIGTTIN|SIGTTOU|SIGIO|SIGXCPU|SIGXFSZ|SIGVTALRM|SIGPROF|SIGWINCH|SIGINFO|SIGUSR1|SIGUSR2,0x0) = 0 (0x0) sigprocmask(SIG_SETMASK,0x0,0x0) = 0 (0x0) sigprocmask(SIG_BLOCK,SIGHUP|SIGINT|SIGQUIT|SIGKILL|SIGPIPE|SIGALRM|SIGTERM|SIGURG|SIGSTOP|SIGTSTP|SIGCONT|SIGCHLD|SIGTTIN|SIGTTOU|SIGIO|SIGXCPU|SIGXFSZ|SIGVTALRM|SIGPROF|SIGWINCH|SIGINFO|SIGUSR1|SIGUSR2,0x0) = 0 (0x0) sigprocmask(SIG_SETMASK,0x0,0x0) = 0 (0x0) process exit, rval = 0 [1] + done sleep 100 Sleep ends immediately instead of waiting for desired number of seconds. I wonder if this is normal behavior or maybe a bug? Checked under 8.2-RELEASE-p3 and 9.0-RELEASE. -- Mateusz Kwiatkowski