Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!ginosko!usc!hacgate!ashtate!dbase!awd
From: awd@dbase.UUCP (Alastair Dallas)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Problem with LSC 4.0 debugger.
Summary: We're waiting...
Message-ID: <256@dbase.UUCP>
Date: 26 Sep 89 18:15:17 GMT
References: <2693@husc6.harvard.edu> <3425@cbnewsc.ATT.COM>
Distribution: na
Organization: Ashton Tate Devlopment Center Glendale, Calif.
Lines: 16

In article <3425@cbnewsc.ATT.COM>, fjo@cbnewsc.ATT.COM (frank.j.owen) writes:
>  I think IF the compiler generated enough information, the debugger
> SHOULD be able to match up all the stuff on the stack correctly.
> It may be true that the CURRENT debugger can't do these things because
> the CURRENT compiler doesn't give it enough information, but that is
> no excuse. Change the compiler. 
> 
>    I think that the feature described in the original posting is a
> useful and valid one. Other compiler/debuggers (I don't know of any in the Mac
> arena - perhaps the Aztec sdb) have this feature. It IS doable. If 
> there are "other issues to consider" that is your job. We just want
> the feature. We don't really care what it takes.

I'm sure we're all waiting to see YOUR compiler/debugger product, Frank.

/alastair/