Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!Teknowledge.COM!polya!Neon.Stanford.EDU!kaufman
From: kaufman@Neon.Stanford.EDU (Marc T. Kaufman)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Problem with LSC 4.0 debugger.
Message-ID: <11950@polya.Stanford.EDU>
Date: 26 Sep 89 03:39:40 GMT
References: <85031@pyramid.pyramid.com> <244@dbase.UUCP> <85347@pyramid.pyramid.com> <254@dbase.UUCP>
Sender: news@polya.Stanford.EDU
Reply-To: kaufman@Neon.Stanford.EDU (Marc T. Kaufman)
Distribution: na
Organization: Stanford University, Computer Science Dept.
Lines: 13

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.

Marc Kaufman (kaufman@Neon.stanford.edu)