Share via

Corrupt Object File

  • Article

Sometimes the linker is unable to process your object files because they are corrupt. Besides the usual causes of corrupt files such as network problems or exposing a floppy disk to a magnetic field, sometimes the compiler writes an incorrect object file, which you should report to Microsoft Product Support Services.

After you have ruled out a hardware, operating system, or network problem as the cause of the corrupt object file, you should try the tips below. Changing compiler options and recompiling sometimes causes the compiler to write a non-corrupt object file.

To fix by using the following possible solutions

  1. Turn off optimization with the /Od (Disable) option.

  2. Disable minimal rebuild with the /Gm– (Enable Minimal Rebuild) option.

  3. Compile with the /Gy (Enable Function-Level Linking) option to package functions.

  4. Use a different code generation option. See the /G (Optimize for Processor) options.

  5. Change the order of functions and global variables.