Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!umich!gumby!smaug!cs.hope.edu!jipping
From: jipping@cs.hope.edu (Mike Jipping)
Newsgroups: comp.sys.transputer
Subject: Re: Using INMOS ANSI C debugger
Message-ID: <1991Jan10.121337.203@cs.hope.edu>
Date: 10 Jan 91 12:13:37 GMT
References: <1991Jan8.201733.29037@netnews.whoi.edu> <LLW.91Jan9102814@corwin.eng.yale.edu>
Sender: news@cs.hope.edu
Reply-To: jipping@cs.hope.edu
Organization: Hope College Dept. of CS
Lines: 29

>    weiman@jargon.whoi.edu (Bob Weiman) writes:
>    ...I am having trouble getting the interactive debugger to run.
> 
> Greetings:
> 
>   We have been using the Inmos ANSI C debugger extensively in both
> interactive and post mortem modes.  It does support both interactive
> and breakpoint debugging on all t8* processors (contrary to some
> incorrect statements made in net postings).  

Hey! That was me! I'm sorry for the misinformation.  I had the same
problem and got the answer I gave from my INMOS support technician.

> ... On the processors without
> breakpoints, the debugger only supports breakpoints on low priority
> processes.

Then allow me to be real naive.  How do I force a process to be a low
priority process.  I'm aching to do breakpoint debugging...

Thanks.

      Mike Jipping
      Hope College Department of Computer Science
      jipping@cs.hope.edu  (BITNET: JIPPING@HOPE)

      "The 70's are over old man.  Take your mood ring and
       go home."
                                   -- Dana Gould