Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!uwvax!umn-d-ub!nic.MR.NET!hal!ncoast!allbery
From: allbery@NCoast.ORG (Brandon S. Allbery)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Problem with LSC 4.0 debugger.
Message-ID: <1989Sep29.025156.24159@NCoast.ORG>
Date: 29 Sep 89 02:51:56 GMT
References: <85031@pyramid.pyramid.com> <244@dbase.UUCP> <6238@pt.cs.cmu.edu>
Reply-To: allbery@ncoast.ORG (Brandon S. Allbery)
Followup-To: comp.sys.mac.programmer
Distribution: na
Organization: North Coast Public Access UN*X, Cleveland, OH
Lines: 32

As quoted from <6238@pt.cs.cmu.edu> by pane@cat.cmu.edu (John Pane):
+---------------
| In article <244@dbase.UUCP> awd@dbase.UUCP (Alastair Dallas) writes:
| >In article <85031@pyramid.pyramid.com>, bjb@pyramid.pyramid.com (Bruce Beare) writes:
| >> The think C 4.0 debugger is not able to show stack variables for
| >> functions that are 1 or more calling frames "up" the stack. 
| >>
| >Does the word 'scope' ring a bell here?  K&R, 1st Ed., p. 76:
| >"The scope of a name is the part of the program over which the name is...
| 
| This has nothing to do with rules of scope.  When a program is running, the
| state of the program includes variables that are in all of the active call
| stack frames.  It is perfectly reasonable to expect a debugger to allow the
| programmer to inspect these values, and in fact most debuggers do.
+---------------

Indeed.  If function x() calls function y() and I have a breakpoint in y() so
I can inspect variables, function x() is still active.  I should be able to
see its local variables and its arguments.  Heck, even System V sdb, an
arguably broken debugger, does this.

Not that I have Think C, just a comment about debuggers,

++Brandon
(P.S.  Quick followup to my past posting on development systems:  I just
bought, used, MPW 2.02 + MPW Pascal.  It'll do, I think.  Anyone want to tell
me otherwise so I'll know how much trouble I'm in?)
-- 
Brandon S. Allbery, moderator of comp.sources.misc	     allbery@NCoast.ORG
uunet!hal.cwru.edu!ncoast!allbery		    ncoast!allbery@hal.cwru.edu
bsa@telotech.uucp, 161-7070 BALLBERY (MCI), ALLBERY (Delphi), B.ALLBERY (GEnie)
Is that enough addresses for you?   no?   then: allbery@uunet.UU.NET (c.s.misc)