From owner-freebsd-current Wed Jun 19 08:54:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA21867 for current-outgoing; Wed, 19 Jun 1996 08:54:17 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA21860 for ; Wed, 19 Jun 1996 08:54:15 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA19234; Wed, 19 Jun 1996 11:54:13 -0400 Date: Wed, 19 Jun 1996 11:54:13 -0400 From: Garrett Wollman Message-Id: <9606191554.AA19234@halloran-eldar.lcs.mit.edu> To: James Raynard Cc: freebsd-current@FreeBSD.ORG Subject: Re: ktrace [Was: 2.2-960612-SNAP resolver problems] In-Reply-To: <199606181341.NAA00521@jraynard.demon.co.uk> References: <9606171557.AA01047@halloran-eldar.lcs.mit.edu> <199606181341.NAA00521@jraynard.demon.co.uk> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk < said: > I don't follow. If the ktrace() system call took a file descriptor > allocated by the ktrace program as its first argument, and used that > to find the vnode to write the trace information to, how would that > involve disturbing the file descriptor table of the process being > debugged? (Except perhaps for pathological cases like trying to get a > running ktrace process to debug itself). The original poster suggested sending it to standard output, which is (generally speaking) not a useful place for binary trace data to go because whatever is interpreting the real output of the program can't deal with it. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant