From owner-freebsd-stable@FreeBSD.ORG Tue Sep 27 13:38:24 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 610EB106566B for ; Tue, 27 Sep 2011 13:38:24 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta04.emeryville.ca.mail.comcast.net (qmta04.emeryville.ca.mail.comcast.net [76.96.30.40]) by mx1.freebsd.org (Postfix) with ESMTP id 484EF8FC13 for ; Tue, 27 Sep 2011 13:38:24 +0000 (UTC) Received: from omta15.emeryville.ca.mail.comcast.net ([76.96.30.71]) by qmta04.emeryville.ca.mail.comcast.net with comcast id dnrg1h0021Y3wxoA4peJms; Tue, 27 Sep 2011 13:38:18 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta15.emeryville.ca.mail.comcast.net with comcast id dpep1h00X1t3BNj8bpepqg; Tue, 27 Sep 2011 13:38:50 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 7382B102C19; Tue, 27 Sep 2011 06:38:23 -0700 (PDT) Date: Tue, 27 Sep 2011 06:38:23 -0700 From: Jeremy Chadwick To: Mark Saad Message-ID: <20110927133823.GA31329@icarus.home.lan> References: <4E819DF7.3060306@gmx.com> <20110927101008.GA27810@icarus.home.lan> <4E81A31B.6080300@gmx.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org Subject: Re: non-responding processes after truss(1)ing 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, 27 Sep 2011 13:38:24 -0000 On Tue, Sep 27, 2011 at 09:28:56AM -0400, Mark Saad wrote: > On Tue, Sep 27, 2011 at 6:19 AM, Nikos Vassiliadis wrote: > > On 9/27/2011 1:10 PM, Jeremy Chadwick wrote: > >> > >> kill -9 your truss processes; the underlying processes which you are > >> truss'ing will probably resume. > >> > >> My experience for years has been that truss on FreeBSD is extremely > >> buggy and cannot be relied upon (case in point). ??Such is still the case > >> on RELENG_8 as of today. > >> > >> Use ktrace(1) instead. ??You'll find it to work pretty much in every > >> situation. > >> > > What about using dtruss in place of truss is the dtrace implementation > of truss any better then the old libkvm ? This pulls in a whole can of worms. Getting DTrace to work on FreeBSD is a little tricky, because certain commands/arguments must be provided manually during world/kernel "make" time and not via make.conf/src.conf. AFAIK this is still the case in RELENG_8, while "kludges and hacks" have been put in place on 9.x to work around this. I can provide some references to my claims if need be. There's also some segregation between DTrace-capable userland and DTrace-capable kernel, but the delineation between the two -- and how to accomplish one without the other -- is something I've never found any conclusive write-up on or otherwise. I think such an explanation would benefit many userland application authors/developers. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |