Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!ames!apple!rutgers!att!cbnewsc!fjo
From: fjo@cbnewsc.ATT.COM (frank.j.owen)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Problem with LSC 4.0 debugger.
Message-ID: <3343@cbnewsc.ATT.COM>
Date: 20 Sep 89 17:31:44 GMT
References: <85031@pyramid.pyramid.com>
Distribution: na
Organization: AT&T Bell Laboratories
Lines: 27

From article <85031@pyramid.pyramid.com>, by bjb@pyramid.pyramid.com (Bruce Beare):
> 
> My complaint is that I can't use the "data" window to look at the

> value of WINDid in Cwindow:Iwindow - because it is a stack variable.
> This behavior of LSC's Debugger is silly. It has all of the information
> it needs - it knows the stack offset of WINDid (it can display it if
> we put a breakpoint in the function Cwindow:Iwindow - before calling 
> CheckResource), and it knows how to trace through the stack frames.

I agree wholeheartedly! It is VERY nice to be able to see the local
variables of all routines in the stack frame. You should also be able
to display the arguements that were passed to those routines. (Afterall,
they are on the stack too.) Register variables are a bit more tricky,
but also do-able, since the stack frame also contains saved values
of the registers used.

The debugger I use here at work (a non-Mac project) has all this and
it is VERY VERY helpful.

Is Rich Siegel listening?

-- 
Frank Owen   312-982-2182
AT&T Bell Laboratories 
5555 Touhy Ave., Skokie, IL  60077
PATH:  ...!att!ihc!fjo