Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!bu.edu!rpi!zaphod.mps.ohio-state.edu!samsung!cs.utexas.edu!yale!cs.yale.edu!corwin.eng.yale.edu!llw From: llw@corwin.eng.yale.edu (Louis L. Whitcomb) Newsgroups: comp.sys.transputer Subject: Re: Using INMOS ANSI C debugger Message-ID: Date: 10 Jan 91 20:06:40 GMT References: <1991Jan8.201733.29037@netnews.whoi.edu> <1991Jan10.121337.203@cs.hope.edu> Sender: news@cs.yale.edu Organization: Yale University, Center for Systems Sciences Lines: 28 Nntp-Posting-Host: corwin.eng.yale.edu In-reply-to: jipping@cs.hope.edu's message of 10 Jan 91 12:13:37 GMT In article <1991Jan10.121337.203@cs.hope.edu> jipping@cs.hope.edu (Mike Jipping) writes: ... How do I force a process to be a low priority process. I'm aching to do breakpoint debugging... Greetings: All processes are low priority unless you specify them to be high priority at either the configuration level or when explicitly running a process with the library functions (e.g. ProcRunHigh and ProcRunLow). To interactively debug a program on a network of B011's attached to a B004 in a pc, for example, use the command line "idebug filename.btl /b /2 /sr" to run the network program under the debugger. Then follow the instructions in Section 8.10 of the Inmos C toolset user manual to set inital breakpoints, run the program, resume after breakpointing, etc. It works well. The Best, -Louis. -- Louis L. Whitcomb llw@corwin.eng.yale.edu ph: (203) 432-4237 Yale Robotics Laboratory fx: (203) 432-7481 Department of Electrical Engineering, 1968 Yale Station, New Haven, CT 06520