Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!henry.jpl.nasa.gov!elroy.jpl.nasa.gov!hacgate!ashtate!dbase!awd
From: awd@dbase.UUCP (Alastair Dallas)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Problem with LSC 4.0 debugger.
Summary: Traceback already available
Message-ID: <258@dbase.UUCP>
Date: 26 Sep 89 19:43:58 GMT
References: <85031@pyramid.pyramid.com> <244@dbase.UUCP> <11950@polya.Stanford.EDU>
Distribution: na
Organization: Ashton Tate Devlopment Center Glendale, Calif.
Lines: 17

In article <11950@polya.Stanford.EDU>, kaufman@Neon.Stanford.EDU (Marc T. Kaufman) writes:
> In article <254@dbase.UUCP> awd@dbase.UUCP (Alastair Dallas) writes:
> 
> >I guess our only continuing disagreement, then, is where to put a global-
> >context debugger on the priority list.  It seems like a lot of pain for
> >only a little gain, to me, so I'd put it fairly low on the list.
> 
> I guess you must never (or seldom) play with recursive functions, such as
> ray tracers or equation solvers.  It's nice to know how you got where you
> are when the stack overflows.
> 
> BTW: I can do this just fine with Jasik's Debugger and MPW.

Function call traceback is already available in the THINK C debugger.  If all
you want is to 'see how you got there' you can do that now.

/alastair/