From owner-freebsd-hackers Mon Apr 23 13:20:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id ECFE637B422 for ; Mon, 23 Apr 2001 13:20:54 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.3/8.11.3) with SMTP id f3NKLBf04225; Mon, 23 Apr 2001 16:21:14 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Mon, 23 Apr 2001 16:21:11 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: diman Cc: freebsd-hackers@freebsd.org Subject: Re: ptrace(PTRACE_SYSCALL,... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sounds like this might also be useful to make a procfs-free truss Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On Mon, 23 Apr 2001, diman wrote: > > Hello, guys > > I'm porting ltrace to FreeBSD and have one little question. > ltrace uses non-standard PTRACE_SYSCALL request, which tells > the kernel to stop traced process on every syscall entry > and notify the parent. > > It makes us possible to trace child's syscalls and *catch > execve/xfork events* and many more. BTW, that request > is non-standard and FreeBSD doesn't support it. > > So, guys, what is a right way for a parent to catch > child making syscall under FreeBSD? I have dosen > k-mode solutions but how to do that from user-space? > > Thanks you very much! > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message