From owner-freebsd-threads@FreeBSD.ORG Sat Feb 24 15:13:58 2007 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9754516A40A for ; Sat, 24 Feb 2007 15:13:58 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id 54FD713C4B7 for ; Sat, 24 Feb 2007 15:13:58 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.14.0/8.14.0/NETPLEX) with ESMTP id l1OFDtXY006411; Sat, 24 Feb 2007 10:13:55 -0500 (EST) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-3.0 (mail.ntplx.net [204.213.176.10]); Sat, 24 Feb 2007 10:13:55 -0500 (EST) Date: Sat, 24 Feb 2007 10:13:54 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Martin Blapp In-Reply-To: <20070224103422.V18301@godot.imp.ch> Message-ID: References: <20070220153632.E4139@godot.imp.ch> <20070220174221.B4139@godot.imp.ch> <20070220190347.C4139@godot.imp.ch> <20070220225303.V4139@godot.imp.ch> <20070220234734.H4139@godot.imp.ch> <20070221000830.V4139@godot.imp.ch> <20070221020335.Y4139@godot.imp.ch> <20070224103422.V18301@godot.imp.ch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: rob@debank.tv, freebsd-threads@freebsd.org Subject: Re: 6.2-Release and Clamd 0.90 with libpthread.so X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Feb 2007 15:13:58 -0000 On Sat, 24 Feb 2007, Martin Blapp wrote: > > Hi, > > After some busy days I found again time to work on this. I still have no clue > what could be responsable for the problems I see. > > ktrace still shows lot of fork()s, but I can't see where whey are called. ktrace is probably lying to you if the code is really only fork()ing once. > Running ktrace with libc_r or libthr I can't see a single call to fork(). > Is ktrace lying to me ? Why do I only see fork()s with libpthread ? The kse upcalls might look like forks to ktrace? -- DE