Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!dalcs!dalcsug!dalegass
From: dalegass@dalcsug.UUCP
Newsgroups: comp.sys.ibm.pc
Subject: Re: QuickC
Message-ID: <144@dalcsug.UUCP>
Date: Thu, 24-Sep-87 06:33:13 EDT
Article-I.D.: dalcsug.144
Posted: Thu Sep 24 06:33:13 1987
Date-Received: Sat, 26-Sep-87 10:01:53 EDT
References: <1485@killer.UUCP> <3320052@hpsrlc.HP.COM> <3826@watdcsu.waterloo.edu> <1373@dataio.Data-IO.COM>
Organization: Dalhousie University, Halifax, N.S., Canada
Lines: 22
Summary: Turbo C global variables works with CodeView

In article <1373@dataio.Data-IO.COM>, bright@dataio.Data-IO.COM (Walter Bright) writes:
> In article <1909@ttrdc.UUCP> kad@ttrdc.UUCP (Keith Drescher) writes:
> #In article <1569@killer.UUCP> richardh@killer.UUCP (Richard Hargrove) writes:
> #My copy of Turbo C does not provide any of the information that
> #codeview needs to perform symbolic debugging.  OK, TurboC will put
> #line numbers in the object file so you can do a combined source/assembly
> #listing, but as far as I can tell you can't access a variable by its
> #symbolic name because TurboC doesn't generate that information.
> 
> Nobody besides Microsoft generates symbolic data for Codeview because
> Microsoft regards the format as proprietary and won't tell anybody.
> 

This is not entirely true.  I use Codeview and Turbo C together regularly.
If you generate a MAP file with Turbo C, and convert that to a SYM file
(using MAPSYM), Codeview will allow references to global variables...
Unfortunately, local variables (on the stack) can not be referenced.

I'm still waiting for TCDEBUG: Judging from TDEBUG, this could be a very
useful and powerful product.

dalegass@dalcsug.uucp