From owner-freebsd-hackers  Sat Dec  7 19:39:00 1996
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id TAA23506
          for hackers-outgoing; Sat, 7 Dec 1996 19:39:00 -0800 (PST)
Received: from kithrup.com (kithrup.com [205.179.156.40])
          by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id TAA23499
          for <freebsd-hackers@freebsd.org>; Sat, 7 Dec 1996 19:38:58 -0800 (PST)
Received: (from sef@localhost) by kithrup.com (8.6.8/8.6.6) id TAA10302; Sat, 7 Dec 1996 19:38:52 -0800
Date: Sat, 7 Dec 1996 19:38:52 -0800
From: Sean Eric Fagan <sef@Kithrup.COM>
Message-Id: <199612080338.TAA10302@kithrup.com>
To: avalon@coombs.anu.edu.au, joerg_wunsch@uriah.heep.sax.de
Subject: Re: truss, trace ??
Cc: freebsd-hackers@freebsd.org
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>Whilst we have ktrace(2) which works with ktrace(1) and kdump(2), there is
>no ptrace(2)

Uh... how do you think gdb talks to processes?  It uses ptrace().

Our ptrace is not sufficient to do syscall stops, though.  I have changes to
procfs and the rest of the kernel that do allow it, however, and I've
written an EP version of truss that uses it.

Sean.