Hi Larry,
 
> :    :run a.b.c; debug
> :    pin #123
> :    tr,i,d
> :    abort
 
The above works even if the program, like OUTSPOOL, is already running ...
and removes the need for determining the Space ID of the program's main
code.
 
Additionally, the ":RUN" technique has another advantage: there is a fair
chance that any XL list that the program needs (and is using) will have
been specified at LINK time, so the ":RUN" will pick up the same XL list, so
that the stacktrace will be much more accurate.  With the "XL ..." method
(coupled with running DEBUG from a different program (e.g., CI.PUB.SYS)),
you won't get the symbolic info from the XLs (except for those XL's that
the process in question has in common with the process you are running
DEBUG from).
 
> :COPY a.b.c,xx
> :debug
> > pin #123
> > tr,i,d              (shows stack without symbols.  Note the space id)
> > xl xx <space id>    (maps program file xx's symbols)
> > tr,i,d              (shows stack with symbols)
 
--
Stan Sieler                                          [log in to unmask]
                                     http://www.allegro.com/sieler.html