Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!snorkelwacker!usc!trwind!venice!press
From: press@venice.SEDD.TRW.COM (Barry Press)
Newsgroups: comp.windows.ms
Subject: Re: CodeView
Message-ID: <369@venice.SEDD.TRW.COM>
Date: 13 Mar 90 17:39:24 GMT
References: <782@venus.UUCP>
Reply-To: press@venice.sedd.trw.com (Barry Press)
Distribution: usa
Organization: TRW Systems Engineering & Development Division, Redondo Beach, CA
Lines: 24

In article <782@venus.UUCP> eric@cfi.COM () writes:
>Could some one who has successfully used 'cvw' with two monitors
>mail me the necessary incantations (compile options, batch files,
>whatever)?  I can get the displays going, but CodeView doesn't know
>anything about the program to be debugged and won't execute it, and
>I don't have the PC experience to proceed.

You need to do several things, none complicated.  First, you must compile
your routines with the -Zi option, which generates cv data in the object
files.  Next, you must link with the /co option, which causes the linker
to pass all that slop on into the .exe.  Finally, assuming I remember the
switches right, you start up cvw roughly like this:

	cvw /2 /l yourprog.exe \path\win.com yourprog.exe

Presumably the version of win.com you point it to is the debugging version,
and is the first version found in the PATH env. var. as well.  You have
to include the full path for win.com.  Finally, I do all this with version
5.1 of C and 2.1x of the SDK.

The /l (letter L) parameter may have been what you missed.  It's what tells
cvw how to find the symbols in your program.
-- 
Barry Press                                 Internet: press@venice.sedd.trw.com