Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!exodus!appserv!sun!amdcad!dgcad!dg-rtp!rti!bcw
From: bcw@rti.rti.org (Bruce Wright)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Codeview for Windows:  Warning CV2206
Summary: OMF errors
Message-ID: <1991Mar21.034742.6244@rti.rti.org>
Date: 21 Mar 91 03:47:42 GMT
References: <1991Mar20.174919.24501@oracle.com>
Organization: Research Triangle Institute, RTP, NC
Lines: 27

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 get this message about 30 times, then the entire system hangs with a UAE
> in Windows.  The <filename> in the message is different each time, and is
> always of a file that has CodeView information compiled into it.  Does
> anyone know
> 
> - What OMF stands for?
> - Why this is happening?
> - What I could do about it?

Could OMF stand for Object Module Format or something along those
lines?  Don't know what you could do about it though, especially
if it is happening in different files.  Does it happen immediately
on startup?  What about if you start Windows up from a clean boot
and immediately start up the offending program - when you do that
does it always happen in the same file name or are the file names
different then too?

Unless you've forgotten to export some routine and/or do a
MakeProcInstance on it - that can cause some oddball errors.  Or
worse, wild pointer manipulations ...

						Bruce C. Wright