From owner-freebsd-hackers Fri May 26 13:52: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from funkthat.com (adsl-63-195-54-213.dsl.snfc21.pacbell.net [63.195.54.213]) by hub.freebsd.org (Postfix) with ESMTP id AEBBE37B86D for ; Fri, 26 May 2000 13:51:57 -0700 (PDT) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by funkthat.com (8.9.3/8.8.7) id NAA28486; Fri, 26 May 2000 13:51:48 -0700 (PDT) Message-ID: <20000526135148.07149@hydrogen.funkthat.com> Date: Fri, 26 May 2000 13:51:48 -0700 From: John-Mark Gurney To: Arun Sharma Cc: FreeBSD Hackers Subject: Re: truss(1) with support for fork(2) and friends References: <20000520180228.A4383@sharmas.dhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <20000520180228.A4383@sharmas.dhs.org>; from Arun Sharma on Sat, May 20, 2000 at 06:02:29PM -0700 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.4-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Arun Sharma scribbled this message on May 20: > I just implemented the "-f" flag in truss, to trace across fork(2), > rfork(2) and vfork(2) (the last one is not tested). [...] > I'm guilty of running indent against the source, before I did this work. > So I can't generate a clean patch yet. But if I get good feedback on this > work, I'll clean it up and produce a patch that can be commited. well, has another committer expressed intrest in this work? I was looking at committing your code, but it's both for an out of date version of truss, and run though ident... if you could provide the changes to the -current source (w/o ident) I'd greatly appreciate it.. -- John-Mark Gurney Voice: +1 408 975 9651 Cu Networking "I say all sorts of useless things." -- cmc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message