Xref: utzoo comp.sys.intel:1102 comp.sys.ibm.pc:43417
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uwm.edu!rpi!crdgw1!ge-dab!tarpit!rtmvax!wbeebe
From: wbeebe@rtmvax.UUCP (Bill Beebe)
Newsgroups: comp.sys.intel,comp.sys.ibm.pc
Subject: Re: C compiler for 80C186
Message-ID: <3082@rtmvax.UUCP>
Date: 2 Feb 90 01:04:59 GMT
References: <1990Jan30.183733.10942@cec1.wustl.edu> <25C74384.19872@paris.ics.uci.edu>
Reply-To: wbeebe@rtmvax.UUCP (Bill Beebe)
Organization: RTmVax Public Unix System, Orlando FL
Lines: 16

In article <25C74384.19872@paris.ics.uci.edu> sklein@ics.uci.edu (Steve Klein) writes:
>Does anyone have any experience using MS-DOS C compilers (specifically
>Microsoft or Watcom) to generate 80x86 code for a standalone ROM
>machine. [material deleted]
>... produce an Intel absolute locate file (such as produced by Intel's
>LOC86), with full symbols ...

My only recomendation is this; if you want to use the Intel ICE, then use
the Intel software tools. They were designed to work together. If you want
to use MSC or Watcom or Turbo or whatever, then look for other ICEs that can
support one or more of the above. Many of the DOS-based C compilers can
produce debugging information that can be mangled into formats
understandable by some of the third party ICEs (or so I've been told).

Mixing Intel debugging hardware with someone elses software tools is like
mixing oil and water.