From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 18 08:24:59 2007 Return-Path: X-Original-To: hackers@freebsd.org 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 823A116A421 for ; Mon, 18 Jun 2007 08:24:59 +0000 (UTC) (envelope-from simias.n@gmail.com) Received: from simias.hd.free.fr (vit94-5-82-243-51-8.fbx.proxad.net [82.243.51.8]) by mx1.freebsd.org (Postfix) with ESMTP id 4FB0813C43E for ; Mon, 18 Jun 2007 08:24:58 +0000 (UTC) (envelope-from simias.n@gmail.com) Received: from simias.hd.free.fr (localhost [127.0.0.1]) by simias.hd.free.fr (8.13.6/8.13.6) with ESMTP id l5I80Rf5012521; Mon, 18 Jun 2007 10:00:27 +0200 (CEST) (envelope-from simias.n@gmail.com) Received: (from simias@localhost) by simias.hd.free.fr (8.13.6/8.13.6/Submit) id l5I80DNJ012501; Mon, 18 Jun 2007 10:00:13 +0200 (CEST) (envelope-from simias.n@gmail.com) X-Authentication-Warning: simias.hd.free.fr: simias set sender to simias.n@gmail.com using -f From: Simias To: Garrett Cooper References: <467636C0.6040604@u.washington.edu> Date: Mon, 18 Jun 2007 10:00:00 +0200 In-Reply-To: <467636C0.6040604@u.washington.edu> (Garrett Cooper's message of "Mon\, 18 Jun 2007 00\:39\:44 -0700") Message-ID: <86ir9lr8u7.fsf@simias.hd.free.fr> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: hackers@freebsd.org Subject: Re: Making sense of ktrace(1) output X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2007 08:24:59 -0000 Garrett Cooper writes: > Ok, so in my effort to find out the choke point for pkg_add, and in > the process I've tried both struss and strace, which have failed > because they weren't tracking the right PID and weren't following > forks (seemed like procfs is all mucked up even though it's mounted > and appears to be working to some extent --only failing 33%~75% of the > time :(..). > > However, I was able to get ktrace output. The only problem is that > ktrace(1) apparently outputs only in binary, instead of plaintext > output. Can I convert it to plaintext somehow and process it? > > Thanks, > -Garrett Yes you can, using kdump(1). -- Simias