Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!samsung!spool.mu.edu!agate!cs.berkeley.edu!jtkohl
From: jtkohl@cs.Berkeley.EDU (John T Kohl)
Newsgroups: comp.unix.bsd
Subject: Re: Trace call in the kernel - what and how to use?
Message-ID: <1286eoINN8k4@agate.berkeley.edu>
Date: 23 Jun 92 21:52:24 GMT
References: <1992Jun20.211805.17936@urbana.mcd.mot.com>
Organization: University of California, Berkeley
Lines: 14
NNTP-Posting-Host: stinson.cs.berkeley.edu
In-reply-to: smadhur@charm.urbana.mcd.mot.com's message of 20 Jun 92 21:18:05 GMT
In article <1992Jun20.211805.17936@urbana.mcd.mot.com> smadhur@charm.urbana.mcd.mot.com (Nivas Madhur) writes:
> I was looking at some code in 4.3BSD kernel and noticed there
> is a trace(...) in most places. Apparently, this can be used
> to get some debugging info. etc. I was wondering if someone
> could explain how to extract this info.
If you're looking at NET-2 derived code, then that's probably the system
call tracing stuff. Look at /usr/src/usr.bin/ktrace/{kdump,ktrace}/* .
--
John Kohl <jtkohl@cs.berkeley.edu>
UC Berkeley CS grad student
Member of the League for Programming Freedom--details: league@prep.ai.mit.edu
(The above opinions are MINE. Don't put my words in somebody else's mouth!)