Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!uwm.edu!uakari.primate.wisc.edu!ginosko!uunet!dino!atanasoff!jwright
From: jwright@atanasoff.cs.iastate.edu (Jim Wright)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Problem with LSC 4.0 debugger.
Message-ID: <1563@atanasoff.cs.iastate.edu>
Date: 25 Sep 89 23:42:43 GMT
References: <244@dbase.UUCP> <3424@cbnewsc.ATT.COM>
Reply-To: jwright@atanasoff.cs.iastate.edu.UUCP (Jim Wright)
Distribution: na
Organization: Iowa State U. Computer Science Department, Ames, IA
Lines: 16

Even though this breaks a much beloved tradition on c.s.m.p., I'm not
flaming anyone...

In article <3424@cbnewsc.ATT.COM> fjo@cbnewsc.ATT.COM (frank.j.owen) writes:
| All the variables of each function are in the stack frame
| for that function and CAN be displayed and even modified. Of course you
| must in some way tell the debugger WHICH stack frame you are talking about,
| in case there are locals of different functions with the same name, but
| that is a do-able thing.

How should recursive functions be handled?  Are they a special case at all?
Do you really want to allow local variables be changed in calling functions?

-- 
Jim Wright
jwright@atanasoff.cs.iastate.edu