Pete Crosby writes:

>My suggestion is to pin to the process and trace it in the same
>command line. This will also allow you to use "DO" or "REDO" to
>repeat the command to get multiple stack traces and thereby an idea of
>what the process is doing.

A tiny tip:

If you issue the DEBUG command SET CRON, DEBUG will repeat the last
command when you just press <return> at the prompt. That saves some
typing when you need to issue the same command repeatedly.

-- Bruce



--------------------------------------------------------------------------
Bruce Toback    Tel: (602) 996-8601| My candle burns at both ends;
OPT, Inc.            (800) 858-4507| It will not last the night;
11801 N. Tatum Blvd. Ste. 142      | But ah, my foes, and oh, my friends -
Phoenix AZ 85028                   | It gives a lovely light.
btoback AT optc.com                |     -- Edna St. Vincent Millay
Unsolicited mail to [log in to unmask] will be inspected for a
fee of US$250. Mailing to said address constitutes agreement to
pay, including collection costs.