Date: Mon, 18 Jun 2007 10:00:00 +0200 From: Simias <simias.n@gmail.com> To: Garrett Cooper <youshi10@u.washington.edu> Cc: hackers@freebsd.org Subject: Re: Making sense of ktrace(1) output Message-ID: <86ir9lr8u7.fsf@simias.hd.free.fr> In-Reply-To: <467636C0.6040604@u.washington.edu> (Garrett Cooper's message of "Mon\, 18 Jun 2007 00\:39\:44 -0700") References: <467636C0.6040604@u.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Garrett Cooper <youshi10@u.washington.edu> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86ir9lr8u7.fsf>