Xref: utzoo comp.unix.wizards:10989 comp.os.misc:506
Path: utzoo!attcan!uunet!husc6!rutgers!ucsd!ames!killer!bigtex!james
From: james@bigtex.uucp (James Van Artsdalen)
Newsgroups: comp.unix.wizards,comp.os.misc
Subject: Re: tracing system calls
Keywords: truss syscall & trace
Message-ID: <7716@bigtex.uucp>
Date: 8 Sep 88 03:34:08 GMT
References: <21606@ccicpg.UUCP> <7622@boring.cwi.nl> <2040@cuuxb.ATT.COM> <7460@bigtex.uucp> <66892@sun.uucp>
Reply-To: james@bigtex.UUCP (James Van Artsdalen)
Organization: F.B.N. Software, Austin TX
Lines: 19

In article <66892@sun.uucp>, brent%terra@Sun.COM (Brent Callaghan) wrote:
> In article <7460@bigtex.uucp>, james@bigtex.uucp (me) writes:

> > > 	$ trace date

> > What on earth does all of this have to do with printing the date and
> > time???  getgid?  ioctl?  That's 36 system calls.

> Most of the system calls in this example are taking care of the
> mapping in of the shared libraries.

How does this implementation compare to the SysVr3 shared libraries?
I had been under the impression there that shared libraries were
mapped into the address space by the kernel, not by the user process.
Is there any particular advantage between the two schemes, or does
SysVr3 do it like Sun OS-4?
-- 
James R. Van Artsdalen    ...!uunet!utastro!bigtex!james     "Live Free or Die"
Home: 512-346-2444 Work: 328-0282; 110 Wild Basin Rd. Ste #230, Austin TX 78746