Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!husc6!mit-eddie!uw-beaver!ssc-vax!uvicctr!sbanner1 From: sbanner1@uvicctr.UUCP (S. John Banner) Newsgroups: comp.sys.ibm.pc Subject: Re: Converting MicroSoft C to Turbo C Message-ID: <261@uvicctr.UUCP> Date: Thu, 25-Jun-87 12:22:50 EDT Article-I.D.: uvicctr.261 Posted: Thu Jun 25 12:22:50 1987 Date-Received: Sat, 27-Jun-87 07:02:26 EDT References: <381@aucs.UUCP> <875@kodak.UUCP> <9797@duke.cs.duke.edu> Reply-To: sbanner1@uvicctr.UUCP (S. John Banner) Distribution: na Organization: University of Victoria, Victoria B.C. Canada Lines: 30 In article <9797@duke.cs.duke.edu> gleicher@duke.UUCP (Michael Gleicher) writes: >As a user of MSC 4.0, and a recent purchaser of Turbo C, I have to >admit, I doubt I'll run MSC too much any more. True CodeView is nice, >but being able to compile in a reasonable time (My hard disk is slow >so the improvement is more than 4X for the program I'm working on). >is worth more than the debugger. >I would think it would be possible to find a way of using TurboC with >Codeview (or some such debugger). TurboC will put line numbers into >the code. I haven't experimented with it. (any comments?) I have played with it, Just compile with the -y option, link using MicroSoft's linker, and the /codeview option, and you are off to the races so to speak. This doesn't give you the variable info, but you have source level tracing/breakpoints, etc, Turbo's libraries have Symbols in them (quite unlike MicroSoft's), though they are not really that useful, I think they are just base addresses for branching, and with the assembler listings in the code, it is not too hard to figure out what machine locations to watch, to use the assembler style watchpoints, instead of symbolic variables. It is not perfect, but it is pretty good (though I do like the Idea of a PC version of DBX). Have Fun, S. John Banner ...!uw-beaver!uvicctr!sol!sbanner1 ...!ubc-vision!uvicctr!sol!sbanner1 ccsjb@uvvm sbanner1@sol.UVIC.CDN