Path: utzoo!attcan!uunet!cs.utexas.edu!usc!bloom-beacon!apple!motcsd!hpda!hpcuhb!hpcilzb!msm
From: msm@hpcilzb.HP.COM (Mark Millard)
Newsgroups: comp.sys.amiga.tech
Subject: Is Lattice CodeProbe usable?
Message-ID: <780004@hpcilzb.HP.COM>
Date: 21 Jul 89 20:57:44 GMT
Organization: HP Design Tech Center - Santa Clara, CA
Lines: 30


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).

I am using Lattice 5.02 and I compiled my program with

     lc -d3 -L main.c

where main.c simply echos any command-line arguments with "printf"
statements.  It compiles and runs perfectly.  Perhaps the debugger
doesn't work with code which is bug free ? ;-)

I am using AmigaDOS 1.3, have two floppy drives, and Commodore's
RAM expansion card, the A2058. No hard drives or bridgecards.
I boot off the Lattice C floppies and invoke CPR from the PopCLI
Shell provided with Lattice.

Although I am not new to C, I am new to Lattice C and CodeProbe,
so I am not aware of any workarounds yet.  Any help would be appreciated.

Thanks,

Mark Millard
E-mail: hplabs!hpdtc!msm
Phone: (408)-866-0531