Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel!munnari.oz.au!uunet!mcsun!Germany.EU.net!news.netmbx.de!zrz.tu-berlin.de!math.fu-berlin.de!hrz.tu-chemnitz.de!wutcd From: wutcd@hrz.tu-chemnitz.de (Joerg Wunsch) Subject: Re: Trace call in the kernel - what and how to use? Message-ID: <wutcd.709317402@hrz.tu-chemnitz.de> Keywords: trace, 4.3 BSD kernel Sender: bin@hrz.tu-chemnitz.de (Owner of all binaries) Organization: tu-chemnitz References: <1992Jun20.211805.17936@urbana.mcd.mot.com> Date: Tue, 23 Jun 1992 16:36:42 GMT Lines: 26 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. Does it log to a device? Yeah, i've seen a device driver information for AT&T-compatible PC/UNIX before (but not the 4.3BSD kernel at all), and i do know that they gave an example there of such a trace driver. Your assumption is correct, there should be such driver which logs the info to a special device. This is one of the common ways of driver debugging (along with kernel printf() statements, but trace is more flexible). Greetings, J"org +----------------------------------------------------------------+ | joerg_wunsch%bonnie@hadrian.hrz.tu-chemnitz.de | |----------------------------------------------------------------+ | J"org Wunsch | If anything can go wrong | | Textil Computer Design GmbH | - it WILL | | R"ahnitzgasse 18 | | | D-O-8060 Dresden (F.R.Germany) | Murphy's Law | +----------------------------------------------------------------+