Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!apple!agate!spam!lippin
From: lippin@spam.berkeley.edu (The Apathist)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Problem with LSC 4.0 debugger.
Message-ID: <1989Oct4.023058.29267@agate.berkeley.edu>
Date: 4 Oct 89 02:30:58 GMT
References: <244@dbase.UUCP> <3424@cbnewsc.ATT.COM> <2633@iscuva.ISCS.COM>
Sender: usenet@agate.berkeley.edu (USENET Administrator;;;;ZU44)
Reply-To: lippin@math.berkeley.edu
Organization: Authorized Service, Incorporated
Lines: 22

Recently jimc@iscuva.ISCS.COM (Jim Cathey) wrote:

>However, at least sdb (in Unix-land) _requires_ you to throw a
>compiler switch that in effect turns off all optimizations in order
>for the code generated to be regular enough for the debugger to pick
>apart.  You then have to recompile anything you want to be able to
>look at or set breakpoints in, or trace stack frames through.  Not
>very elegant, and the code you're debugging ends up very different
>than the code that had the problem (unless you always use the grunge
>switch).

Similarly, in LSC there's the "gray diamond" switch to be thrown.  You
can't debug a file unless it was compiled with switch on, it turns off
all optimization (as there isn't any to speak of to begin with), and
it increases the size of your project file.  So what's the difference?

					--Tom Lippincott
					  lippin@math.berkeley.edu

    "This view derives partly from what is known as common sense,
     whose virtue, uniquely among virtues, is that everyone has it."
					--Tom Stoppard, _Jumpers_