This topic is 4700 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

## Recommended Posts

When I try to compile my project for DEBUG (OK for RETAIL), I get the following message...
dinput8.lib(dilib2.obj) : fatal error LNK1103: debugging information corrupt; recompile module

... the MSDN docs say...
Linker Tools Error LNK1103
debugging information corrupt; recompile module

Possible cause

The compilation was terminated before a valid object file was created.
Recompile the given object file. If recompiling does not correct the problem,
note the circumstances of the error, try to isolate the problem, and create a
reproducible test case. Then consult the technical-support help file, the
technical-support section in one of your manuals, or Microsoft Product Support
Services.


... and...
Corrupt Object File
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.

Possible solutions

Turn off optimization with the /Od (Disable) option.
Disable minimal rebuild with the /Gm– (Enable Minimal Rebuild) option.
Compile with the /Gy (Enable Function-Level Linking) option to package functions.
Use a different code generation option. See the /G (Optimize for Processor) options.
Change the order of functions and global variables

... I have tried all the build switches. Thanks for any help

##### Share on other sites
You can also find this information in the Forum FAQ. The only entry in red.

##### Share on other sites
Apologies, I must have read it pre-December 2004.

Small typo in the FAQ... "VC++6. 0is"

##### Share on other sites
Quote:
 Original post by LemonLimeApologies, I must have read it pre-December 2004.

No big deal [smile]

Quote:
 Small typo in the FAQ... "VC++6. 0is"

The FAQ's filled with similar errors, unfortunately. This comes from a bug somewhere in my system. Basically, whenever I copy some text and paste it (from or to a borwser), it borks spaces like this.

##### Share on other sites
Quote:
 The FAQ's filled with similar errors, unfortunately.

Yes, my brain read it as...

Quote:
 The only issue is (with?) that the D3DX.lib you need to use with VC++6. Ols (is?) in the DirectX9.0c Summer 2004 Extras package.

... :D

BTW, any chance of a little green icon on the forum FAQ (like recent posts) so you see when it has been updated?

[Edited by - LemonLime on September 4, 2005 11:28:35 AM]

##### Share on other sites
Quote:
 BTW, any chance of a little green icon on the forum FAQ (like recent posts) so you see when it has been updated?

That's a pretty good suggestion. Can you please take it to the "GDNet Comments, Suggestions and Ideas" forum? The staff will take it from there.

##### Share on other sites
Sure... posted here.

1. 1
Rutin
23
2. 2
3. 3
JoeJ
20
4. 4
5. 5

• 9
• 33
• 41
• 23
• 13
• ### Forum Statistics

• Total Topics
631745
• Total Posts
3002005
×