Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!decwrl!fernwood!oracle!news
From: mwick@.com (Mark Wick)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Codeview for Windows:  Warning CV2206
Message-ID: <1991Mar24.031338.27262@oracle.com>
Date: 24 Mar 91 03:13:38 GMT
References: <1991Mar20.174919.24501@oracle.com> <356@intertel.UUCP>
Reply-To: mwick@oracle.UUCP (Mark Wick)
Organization: Oracle Corporation, Belmont, CA
Lines: 18

In article <356@intertel.UUCP> boyd_m@intertel.UUCP (Mark Boyd) writes:
>In article <1991Mar20.174919.24501@oracle.com>, mwick@.com (Mark Wick) writes:
>> 
>> Has anyone else had this problem:
>> 
>> CV2206 Warning: Corrupt Debug OMF found in <filename>.  Deleting source
>> line.
>> 
>
>I've had this same error.  It turned out to be the linker was putting out
>debugging information for the Windows 2.10 version of CVW (were using OPTLINKS
>by SLR systems).  My guess is that you're using LINK4 and then trying to use
>Windows 3.0 and CVW.

It turns out that it is a bug in the current version of the Microsoft
Linker (5.10).  And using OptLinks appears to be the only solution...

Mark