From owner-freebsd-hackers Tue Apr 24 6: 9:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sivka.carrier.kiev.ua (sivka.carrier.kiev.ua [193.193.193.101]) by hub.freebsd.org (Postfix) with ESMTP id 582AF37B422; Tue, 24 Apr 2001 06:09:20 -0700 (PDT) (envelope-from diman@asd-g.com) Received: from core.is.kiev.ua (p187.is.kiev.ua [62.244.5.187] (may be forged)) by sivka.carrier.kiev.ua (8/Kilkenny_is_better) with ESMTP id QDO25212; Tue, 24 Apr 2001 16:09:14 +0300 (EEST) (envelope-from diman@asd-g.com) Received: from [10.203.1.10] ([10.203.1.10]) by core.is.kiev.ua (8.11.1/ASDG-2.3-NR) with ESMTP id f3OD9CQ45316; Tue, 24 Apr 2001 16:09:12 +0300 (EEST) (envelope-from diman@asd-g.com) Date: Tue, 24 Apr 2001 14:06:36 +0000 (GMT) From: diman X-Sender: diman@portal.none.ua To: Robert Watson 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 Thank you much, procfs events really helps ! To make truss work without procfs mounted, it's easy to cut 1 line of PIOCBIS procfs_ioctl() code and put it to a new PTRACE_SYSCALL ptrace() request - really it is a same things with different names. Then replace all open/read/write/close with respective ptrace() calls and umount /proc =) I want port to work on older FreeBSD systems too, so now I'll use fcntl.h. On Mon, 23 Apr 2001, Robert Watson wrote: > > 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! > > Thanks & Peace To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message