Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!spool2.mu.edu!uunet!mcsun!ukc!inmos!nigel@dodo.inmos.co.uk From: nigel@dodo.inmos.co.uk (Nigel Holder) Newsgroups: comp.sys.transputer Subject: Re: Using INMOS ANSI C debugger Message-ID: <13525@ganymede.inmos.co.uk> Date: 9 Jan 91 09:55:46 GMT References: <1991Jan8.201733.29037@netnews.whoi.edu> Sender: news@inmos.co.uk Reply-To: nigel@inmos.co.uk (Nigel Holder) Organization: INMOS Limited, Bristol, UK. Lines: 37 In article <1991Jan8.201733.29037@netnews.whoi.edu> weiman@jargon.whoi.edu (Bob Weiman) writes: > >If someone is using the new Inmos ANSI C compiler and >toolset perhaps they could anwer a qustion for me. I am >having trouble getting the interactive debugger to run. >I am using a T800 as the debugger TRAM. I have heard >a rumor that you a T801 or T425 for the debugger TRAM >because they have some breakpointing instructions that >th T800 doesn't have. Is this true? >-- >Bob Weiman Internet: bweiman@whoi.edu The rumour is true that the T425 and T801 have extra instructions to support breakpointing *but* we do document them so it's not really a rumour. However, as far as using the new breakpoint debugger is concerned, the debugger itself requires *any* 32 bit transputer with at least 1 Mbyte (preferably 2 Mbyte) for itself; the rest of the network can consist of any combination of 16 and 32 bit transputers. Setting breakpoints on transputers without hardware breakpoint support (eg. T800, T222 etc.) is still possible with idebug so long as you only set them in low priority processes. This is of course mentioned in the documentation for idebug - have you read it or is it unclear ? (if so tell me for future incorporation). Have you phoned your local INMOS Business Center for help with using the toolset ? (as listed in the toolset documentation). Nigel Holder, Software Group, INMOS Ltd | Tel +44 454 616616 1000 Aztec West | Almondsbury | UK: nigel@uk.co.inmos Bristol BS12 4SQ, UK | US: nigel@inmos.com