Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!mcvax!ukc!reading!sjf
From: sjf@reading.ac.uk (Steve Fisher)
Newsgroups: comp.sys.amiga.tech
Subject: Lattice 5.02 & CodeProbe 1.02
Keywords: Lattice 5, CodeProbe
Message-ID: <1435@onion.reading.ac.uk>
Date: 2 May 89 17:21:53 GMT
Organization: Reading University, UK
Lines: 38

I have an A500 (PAL) with 1 Meg and an extra disk drive, I have
experienced amazing problems with CodeProbe to the extent
that is is really unusable.
  For example when trying to step through the lines.c demo
I get as far as opening the window & then hello GURU.
The GURU is usually 3 or 4 and the address corresponds to
that given as the task address on the Dialogue window.

To get to this stage I have used the standard floppy
startup of disk 1 & 2, I have then compiled the file
on disk 4 in examples/debugger/lines.c with the command
line :  lc -d3 -La lines

This produces code which runs fine & even steps through OK
with the MetaScope debugger.

However on loading into cpr with cpr lines, I get the good
old GURU after opening the window.
I have tried cpr -w -t df1:temp lines, to get extra mem.,
then I tried setting break points after the open window
all give the GURU.
I have even tried it on a differnt C program of my own.
This one opend a Screen, and yes you guessed, GURU on
opening the screen.

Can someone from Lattice please help me on this.
CodeProbe was my reason for buying v5 and it looks really
good if only it would work!!!!

In case you are wondering I brought this from a dealer in
the UK and there was no registration card. The dealer has
said he will send one as he has contacted the distributor,
but until this happens I cannot register for upgrades.
Please can someone help, is it me or Codeprobe?
-- 
//  --   Steve Fisher   Micro. Unit. Computer Science Dept.
\\ |--        &                                      >  Reading University
//.||.   Shawn Fraser   Cybernetics Dept.