From owner-freebsd-hackers  Mon Dec 26 23:26:33 1994
Return-Path: hackers-owner
Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id XAA10093 for hackers-outgoing; Mon, 26 Dec 1994 23:26:33 -0800
Received: from csc.canberra.edu.au (csc.canberra.edu.au [137.92.1.1]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id HAA10084 for <hackers@freebsd.org>; Tue, 27 Dec 1994 07:26:21 GMT
Received: from student.canberra.edu.au by csc.canberra.edu.au (5.65/1.35)
	id AA09603; Tue, 27 Dec 94 18:25:21 +1100
Received: by student.canberra.edu.au (5.0/SMI-SVR4)
	id AA05486; Tue, 27 Dec 94 18:25:01 EDT
Date: Tue, 27 Dec 1994 18:25:00 +1100 (EDT)
From: "Gasparovski / Daniel (ISE)" <u923168@student.canberra.edu.au>
X-Sender: u923168@student
To: hackers@freebsd.org
Subject: ptrace
Message-Id: <Pine.SOL.3.91.941227181731.5398B-100000@student>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 439
Sender: hackers-owner@freebsd.org
Precedence: bulk


A quick question.  Is there anything in FreeBSD which does what the 
PTRACE_SYSCALL option should do in ptrace(2)?  I've poked around in the 
sources (PTRACE_ATTACH and PTRACE_DETACH, though broken, can be acheived 
through procfs.. but no PTRACE_SYSCALL) but havn't found anything yet.

Or do I have to use PTRACE_SINGLESTEP and pray to the BSD gods? (yuk)
(still not sure how I'd detect syscalls, but shouldn't be *that* hard)

Dan ...