From owner-freebsd-ports Tue Nov 7 17:40:49 1995 Return-Path: owner-ports Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA12047 for ports-outgoing; Tue, 7 Nov 1995 17:40:49 -0800 Received: from hutcs.cs.hut.fi (root@hutcs.cs.hut.fi [130.233.192.2]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id RAA12042 for ; Tue, 7 Nov 1995 17:40:46 -0800 Received: from shadows.cs.hut.fi by hutcs.cs.hut.fi with SMTP id AA20240 (5.65c8/HUTCS-S 1.4 for ); Wed, 8 Nov 1995 03:40:37 +0200 Received: (hsu@localhost) by shadows.cs.hut.fi (8.6.10/8.6.10) id DAA06163; Wed, 8 Nov 1995 03:40:51 +0200 Date: Wed, 8 Nov 1995 03:40:51 +0200 Message-Id: <199511080140.DAA06163@shadows.cs.hut.fi> From: Heikki Suonsivu To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: freebsd-ports@freebsd.org In-Reply-To: J Wunsch's message of 7 Nov 1995 05:25:01 +0200 Subject: Re: port of strace? Sender: owner-ports@freebsd.org Precedence: bulk As Paul Fox wrote: > hi -- is anyone aware of a porting effort for the "strace" command? Hmm, we've got ktrace already. Where's the difference? strace (trace on SunOS, truss on Solaris) is much less clumsy to use, just say strace -p , watch system calls go by, and detach with INTR. ktrace wants a file (bad) and needs separate command (kdump) to watch what was going on (too late). ktrace has more features, probably, but I do miss (s)trace, it has been really helpful tracking down various problems. -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@cs.hut.fi home +358-0-8031121 work -4513377 fax -4555276 riippu SN