From owner-freebsd-stable@FreeBSD.ORG Tue Apr 11 13:21:22 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 66D2016A402 for ; Tue, 11 Apr 2006 13:21:22 +0000 (UTC) (envelope-from jonas.wolz@freenet.de) Received: from mout1.freenet.de (mout1.freenet.de [194.97.50.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3815442A6 for ; Tue, 11 Apr 2006 13:21:21 +0000 (GMT) (envelope-from jonas.wolz@freenet.de) Received: from [194.97.50.138] (helo=mx0.freenet.de) by mout1.freenet.de with esmtpa (Exim 4.61) (envelope-from ) id 1FTIo4-0004jd-Vz for freebsd-stable@freebsd.org; Tue, 11 Apr 2006 15:21:20 +0200 Received: from p54a439cb.dip0.t-ipconnect.de ([84.164.57.203] helo=pc1) by mx0.freenet.de with esmtpsa (ID jonas.wolz@freenet.de) (TLSv1:AES256-SHA:256) (Exim 4.61-RC1 #1) id 1FTIo4-0000fs-Op for freebsd-stable@freebsd.org; Tue, 11 Apr 2006 15:21:20 +0200 Received: from jonas by pc1 with local (Exim 4.50) id 1FTInz-00039M-P7 for freebsd-stable@freebsd.org; Tue, 11 Apr 2006 15:21:15 +0200 From: Jonas Wolz To: freebsd-stable@freebsd.org Date: Tue, 11 Apr 2006 15:21:15 +0200 User-Agent: KMail/1.7.2 References: <200604101145.26621.jonas.wolz@freenet.de> In-Reply-To: <200604101145.26621.jonas.wolz@freenet.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604111521.15572.jonas.wolz@freenet.de> Subject: Re: truss problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Apr 2006 13:21:22 -0000 Am Montag, 10. April 2006 11:45 schrieb Jonas Wolz: > Other applications I tested (xedit, bash) seem to work fine. I've made some more tests and it seems to me that the "fork following" feature (-f switch) of truss obviously is buggy. Even the following simple shell script sometimes (in about a third of the tests) provokes the bug: -- begin test.sh #!/bin/sh /bin/echo Test /bin/echo Test -- end test.sh If I call "truss -f sh test.sh" I get errors when execve() is called to start /bin/echo, for example: (56179 is the first /bin/echo (started without error), 56178 is /bin/sh) 56179: writev(0x1,0x804b030,0x2) = 5 (0x5) 56179: exit(0x0) process exit, rval = 0 56178: wait4(0xffffffff,0xbfbfde98,0x2,0x0) = 56179 (0xdb73) 56178: fork() = 56181 (0xdb75) 56178: getpgrp() = 56177 (0xdb71) 56181: close(10) = 0 (0x0) 56181: execve("/bin/echo",,) truss: PIOCWAIT top of loop: Input/output error 56181: execve("/bin/echo",,) = 0 (0x0) 56181: mmap(0x0,3600,(0x3)PROT_READ|PROT_WRITE,(0x1000)MAP_ANON,-1,0x0) = 671539200 (0x2806e000) 56181: munmap(0x2806e000,0xe10) = 0 (0x0) 56181: __sysctl(0xbfbfded8,0x2,0x2806aa18,0xbfbfded4,0x0,0x0) = 0 (0x0) I also tested the script with the 6.1-BETA4 Boot-CD. The bug seems only to be triggered on the *first run* of the script there, but it leaves 3 zombie processes per run behind (even if no error message is shown). Jonas