From owner-freebsd-questions  Mon Apr 15 12:12:42 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id MAA24652
          for questions-outgoing; Mon, 15 Apr 1996 12:12:42 -0700 (PDT)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA24636
          for <freebsd-questions@freebsd.org>; Mon, 15 Apr 1996 12:12:39 -0700 (PDT)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA09297; Mon, 15 Apr 1996 12:09:43 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199604151909.MAA09297@phaeton.artisoft.com>
Subject: Re: "truss" clone for FreeBSD?
To: Harlan.Stenn@pfcs.com (Harlan Stenn)
Date: Mon, 15 Apr 1996 12:09:43 -0700 (MST)
Cc: freebsd-questions@freebsd.org
In-Reply-To: <20302.829540989@mumps.pfcs.com> from "Harlan Stenn" at Apr 15, 96 00:03:09 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Is there a "truss" clone for FreeBSD?

You can use "ktrace", which is obnoxious to use.

Sean Eric Fagan has implemented a working "truss" that doesn't
require all of the "dump file/undump file" crap.

If you are tracking a problem that causes a machine crash, ktrace
is pretty damn useless for finding the area of the code causing
the crash because it doesn't provide sufficient feedback, and the
data which would be useful after post-processing is lost in a
kernel buffer when a crash occurs.

I suggest contacting Sean directly.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.