sjf@reading.ac.uk (Steve Fisher) (05/03/89)
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.
cmcmanis%pepper@Sun.COM (Chuck McManis) (05/04/89)
In article <1435@onion.reading.ac.uk> sjf@reading.ac.uk (Steve Fisher) writes: > 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. Codeprobe 1.02 must have the stack set for it. So on your CLI type STACK 25000 before running codeprobe. That should cure your problem. This is a known problem (it was mentioned a couple of times in the BIX lattice conference) they said it would be fixed in 5.0.3 or 5.1 whichever came first. --Chuck McManis uucp: {anywhere}!sun!cmcmanis BIX: cmcmanis ARPAnet: cmcmanis@sun.com These opinions are my own and no one elses, but you knew that didn't you. "A most excellent barbarian ... Genghis Kahn!"
mroth@ihlpf.ATT.COM (Roth) (05/06/89)
In article <1435@onion.reading.ac.uk> sjf@reading.ac.uk (Steve Fisher) writes: >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. > >// -- Steve Fisher Micro. Unit. Computer Science Dept. >\\ |-- & > Reading University >//.||. Shawn Fraser Cybernetics Dept. This sounds like you are running out of stack space for CodeProbe. I believe that CodeProbe for Lattice 5.02 needs more stack space than version 5.0 did. I would suggest setting the stack space to something like 32768 (32K). You should run into very few stack problems this way (unless you allocate large arrays on the stack). ----- Mike Roth ---------------------------------- att!ihlpf!mroth ----------------------------------