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