Click above to get retro games delivered to your door ever month!

 Microsoft CodeView debugger
------------------------------------------------------------------------------
 Note: The Microsoft CodeView debugger CANNOT be used to debug DOS extended
 programs, to do so requires a protected mode debugger such as NuMega
 SoftICE/W.

 Blinker supports CodeView debugging of Windows programs and DOS real mode
 programs with compilers that produce CodeView information levels 0, 1, 2 and
 5. This encompasses all MS compilers through C/C++ version 7.x and Visual
 C++ (C8), Visual BASIC for DOS 1.0, BASIC PDS 7.1, Pascal 4.0, Fortran 5.0
 and MASM 6.x. At the time of writing, other manufacturer's compilers that
 produce CodeView information comply with this requirement.

 Overlays and CodeView versions 1 - 3

 In order for Blinker to provide compatibility with the older versions of
 CodeView and still retain the advantages of dynamic overlaying, Blinker
 creates a static overlay area, the size of which is determined by the
 largest overlaid object module, within the executable image. At program
 execution time, the overlay manager will identify those modules that are
 within a 'CodeView area' and copy them into the static area for execution.
 The creation of the static overlay area within the program image will
 increase the load size of the program by the size of the largest overlaid
 module for which CodeView information is active.

 In order to allow you to single step and trace into overlaid modules,
 Blinker will create a source file with the same name as the executable, but
 with the extension .VEC. This file should be made available to CodeView at
 program execution time, as if it were one of your own source files. When
 tracing your program, follow the directions given in this source file as to
 when to step over, and when to step into, the overlay vectors and overlay
 manager.

 There is a penalty in execution speed while debugging overlaid code under
 the older versions of CodeView, which is primarily caused by the overlay
 manager having to copy modules into the static overlay area. In effect this
 causes a worst case overlay situation whereby modules are being constantly
 swapped in and out of a single memory area, the impact of which will vary
 depending on the program (and modules) being debugged. There are two things
 that can be done to help alleviate this problem:

 . Limit the amount of code that is to be debugged by using CodeView
   areas

 . Increase the size of the overlay cache to speed up overlay
   operations