;
12/23/94

 This program contains material from the ORCA/C Run-Time Libraries,
 copyright 1987-1994 by Byte Works, Inc. Used with permission.

Trace is a very simple, slightly useful, shell utility. I often find that
when I am about to start testing a new utility, I wish I'd put a DebugStr()
near the start, but I dread another compile/link to insert one line.
So, trace basically prefixes a command line with DebugStr().
You can often replace it with a well chosen os break or tool break.
At the worst, you can break on calls in the ORCA root, like
NewHandle or, guessing, GetDevNumber, DInfo, DControl, SANEStartUp.
Damn, I guess it just wasn't needed. Oh well. It is a little more
convenient than setting a tool break at least.

Run trace with no parameters for a brief usage statement. The i/o requires
ORCA/Shell 2.0.1 or later or GNO ? and probably System 6.0 or later.
Other than printing the usage string, trace should work with any version
of anything, though it requires GSBug to be installed and it to be new enough
to support the DebugStr() call. Trace will _crash_ if GSBug is not installed
and handling DebugStr(). Without GSBug, there is no point in trace anyway

Source is included. Libraries and headers to allow actually building the source
should be available soon. Nag me if you want them out sooner rather than
later or never.

Trace is not a very good name. I wanted to use 'debug', but I believe that
is taken by the obsolete shell version of GSBug.

If you are tracing an ORCA/C program, GSBug's X command is useful for
skipping over the environment initialization. The 'root' is typically:

   jsl setup
   pea
   plb
   plb
   jsl more_setup
   jsl main
   jsl shutdown

You'll want to 'X over' the first two setup's to get to your code quickly.

 Jay Krell
 jay.krell@cornell.edu
 jay.krell@genie.geis.com (ie: jay.krell on GEnie)