Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!husc6!endor!singer
From: singer@endor.harvard.edu (Rich Siegel)
Newsgroups: comp.sys.mac.programmer
Subject: Re: LSC almost gets it right.
Message-ID: <326@husc6.harvard.edu>
Date: 11 Sep 88 01:03:05 GMT
References: <5077@fluke.COM> <526@bruce.oz> <5125@fluke.COM>
Sender: news@husc6.harvard.edu
Reply-To: singer@endor.UUCP (Rich Siegel)
Organization: Symantec/THINK Technologies, Bedford, MA
Lines: 25

In article <5125@fluke.COM> mce@tc.fluke.COM (Brian McElhinney) writes:
>
>And will the debugger be updated to let you look at all stack frames?  LSC's
>is the first symbolic debugger I have seen that only lets you look at the top
>frame.  Surely I'm not the only one who digs into calling stack frames in
>search of the Last Bug...

	As documented, if you hold down the mouse button on the current
function name, a popup menu gives you the call chain, and selecting an
item from this menu takes you to that procedure. (Assuming, of course, that
you've compiled that procedure with debug tables in.))

R.




Rich Siegel
Staff Software Developer
THINK Technologies Division, Symantec Corp.
Internet: singer@endor.harvard.edu
UUCP: ..harvard!endor!singer
Phone: (617) 275-4800 x305

Any opinions stated in this article do not necessarily reflect the views
or policies of Symantec Corporation or its employees.