Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!decwrl!ucbvax!f4.n494.z5.fidonet.ORG!011HFAA.WITSVMA
From: 011HFAA.WITSVMA@f4.n494.z5.fidonet.ORG (011HFAA WITSVMA)
Newsgroups: comp.sys.transputer
Subject: (none)
Message-ID: <1154.26E5FD75@puddle.fidonet.org>
Date: 6 Sep 90 13:19:40 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 33

Re : Occam Debugger
 
We've installed a Parsytec SuperCluster (16 T800s), and have been develo-
ping occam programs using Multi Tool 5.0.
 
The debugger works perfectly on all the processors in the network,
** except ** for the 1st one (i.e. Processor 0).
 
When trying to debug code on Processor 0, the debugger does some weird
things. To illustrate one instance of its behaviour, take the following
example :
 
  IF
    x = 7
      STOP
    TRUE
      SKIP
 
Once the processor has halted on the above STOP command, the debugger
will locate this point in the program. However, should one try to
"INSPECT" the value of x, it returns some arbitrary integer value.
 
As I said, for all other processors in the network, the debugger is
fine - it only gives problems with regard to the first one.
 
Any ideas, comments, similar experiences, ... ?
 
-- Craig
 
E-Mail  : 011hfaa.witsvma@f4.n494.z5.fidonet.org
--  
uucp: uunet!m2xenix!puddle!5!494!4!011HFAA.WITSVMA
Internet: 011HFAA.WITSVMA@f4.n494.z5.fidonet.org