Path: utzoo!attcan!uunet!seismo!ukma!wuarchive!gem.mps.ohio-state.edu!uwm.edu!rpi!batcomputer!cornell!rochester!pt.cs.cmu.edu!cat.cmu.edu!pane
From: pane@cat.cmu.edu (John Pane)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Problem with LSC 4.0 debugger.
Message-ID: <6238@pt.cs.cmu.edu>
Date: 22 Sep 89 21:49:22 GMT
References: <85031@pyramid.pyramid.com> <244@dbase.UUCP>
Distribution: na
Organization: Carnegie-Mellon University, CS/RI
Lines: 27

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. 
>>
>>	<example deleted>
>>
>> 
>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.

John Pane						pane@cs.cmu.edu
School of Computer Science 
Carnegie Mellon University				(412) 268-5884
--
John Pane						pane@cs.cmu.edu
School of Computer Science 
Carnegie Mellon University				(412) 268-5884
-- 
John Pane						pane@cs.cmu.edu
School of Computer Science 
Carnegie Mellon University				(412) 268-5884