Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!gatech!mcnc!rti!sas!walker
From: walker@sas.UUCP (Doug Walker)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Is Lattice CodeProbe usable?
Message-ID: <1120@sas.UUCP>
Date: 31 Jul 89 15:44:49 GMT
References: <780004@hpcilzb.HP.COM>
Reply-To: walker@sas.UUCP (Doug Walker)
Organization: SAS Institute Inc, Cary NC
Lines: 17

In article <780004@hpcilzb.HP.COM> msm@hpcilzb.HP.COM (Mark Millard) writes:
>
>I'm having problems with the Lattice C debugger, CodePRobe, and was
>wondering if anybody else has seen these symptoms.  The tool will
>GURU while simply stepping through a program (via <cr>) or a mouse
>click (when accessing the menus).  It usually happens after successfully
>stepping through the program once, and using the "restart" command to
>re-execute the process.  I see this every time I try to use it (last night
>it happened 15 times within an hour).

There is a known bug in CPR that causes it to divide its stack by four; try
bumping your stack size (via the CLI STACK command) to 60000 or so.

And, er, if it crashes when you use the 'restart' command, one workaround
might be to ... not use it?  You can always exit CPR and invoke it again.

--Doug