Path: utzoo!attcan!uunet!cs.utexas.edu!yale!quasi-eli!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: 9 Jan 91 15:28:14 GMT References: <1991Jan8.201733.29037@netnews.whoi.edu> Sender: news@cs.yale.edu Organization: Yale University, Center for Systems Sciences Lines: 33 Nntp-Posting-Host: corwin.eng.yale.edu In-reply-to: weiman@jargon.whoi.edu's message of 8 Jan 91 20:17:33 GMT In article <1991Jan8.201733.29037@netnews.whoi.edu> 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). On the processors without breakpoints, the debugger only supports breakpoints on low priority processes. Note that your processors need a fair amount of memory to run the debugger. Note also that, since the debugger is written to support a multitude of target configurations, you need to correctly involk it with command line switches corresponding to your network. For example, to run the debugger in post mortem mode on a network of B011s from a PC with a B004 development card, we use the command "idebug filename.btl /t 2 /sa /a". Read the Inmos documentation carefully to get the switches right for your configuration. Perhaps you could be more specific about what sor of trouble you are having? 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