Date: Mon, 23 Apr 2001 16:21:11 -0400 (EDT) From: Robert Watson <rwatson@freebsd.org> To: diman <diman@asd-g.com> Cc: freebsd-hackers@freebsd.org Subject: Re: ptrace(PTRACE_SYSCALL,... Message-ID: <Pine.NEB.3.96L.1010423103822.99299A-100000@fledge.watson.org> In-Reply-To: <Pine.BSF.4.21.0104231302260.223-100000@portal.none.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1010423103822.99299A-100000>