How to slove this error? Fatal error LNK1103: debugging information corrupt; recompile module

Question

0.00/5 (No votes)

See more:

fatal error LNK1103: debugging information corrupt; recompile module
what is the cause of this error and how to solve it?

What I have tried:

fatal error LNK1103: debugging information corrupt; recompile module

Posted 7-Sep-17 0:17am

Naveen_vemuri

Updated 18-Sep-17 23:56pm

Add a Solution

Comments

Jochen Arndt 7-Sep-17 6:46am

Which VS version?
Is the module build by you or is it a 3rd party module?
Has it been build with the same VS version as your project?

The error should vanish when building the module with the same VS version as the project.

Naveen_vemuri 7-Sep-17 7:59am

it was written in VS2008 version.Now i am converting into VS2017 version and building using VS2017 verion.

Jochen Arndt 7-Sep-17 8:09am

So you are trying to link a version build with 2008 with a 2017 project build?

Build all with 2017. Check also your project settings. Maybe you have still a path to the old module in your converted project so that a new module version is build but the old is still used to be linked from the project.

Naveen_vemuri 7-Sep-17 9:08am

Still the problem is not resolved.Is there a way to find which old module is linking?i tried verbose also but didn't find anything.

Jochen Arndt 7-Sep-17 9:15am

The error message contains the name of the module. Find that in the verbose output and check the path.

If that is wrong (path to old version), check your project settings (linker path settings and order and for modules specified with full path).

Naveen_vemuri 8-Sep-17 1:41am

The paths are correct only.i will give u a clear view about the problem.
i have a project named "3DCP.sln".it has five projects
1.3DAppLib
2.3DAppTest
3.3DEngine
4.Tools
5.Win32Emu.
Each of them have no dependency on other except 3DAppTest which depends on all the other four projects.I converted every project from vs2008 to vs2017 and they are building fine except 3DAppTest which gives the above error.The error occurs in 3DAppTest project and in file Win32Emu.lib which is the output file for win32Emu project which is used by this project.

Jochen Arndt 8-Sep-17 2:54am

You might add this to your question so that others see it immediately too and might help (use the green 'Improve question' link).

With the above, all I can still suggest is to check that the win32emulib is actual (date check) and that it is linked (rebuild all, build lib before project).

If you are still not able to resolve the issue you might create the lib as release only and link that with the debug build of your project.

You might also create a small test project that calls one function from the library and see if that generates the error too. If not, there is something wrong with your setup.

Depend the other projects also on that library? Then you have to check them too (other projects linked against an old version).

Naveen_vemuri 11-Sep-17 7:16am

i have seen in some posts that this error is in latest version of visual studio 15.3 and not with 15.0 and 15.2.do you know anything about it?

Jochen Arndt 11-Sep-17 7:19am

Sorry, no.

Naveen_vemuri 15-Sep-17 5:20am

in the above error it is saying "recompile module".what does that mean? and how to recompile that?
"The error occurs in 3DAppTest project and in file Win32Emu.lib which is the output file for win32Emu project which is used by this project."

Jochen Arndt 15-Sep-17 5:37am

It means you have to recreate the mentioned file(s) (Win32Emu.lib, Win32Emu.dll) by doing a rebuild for the corresponding project.

Naveen_vemuri 15-Sep-17 5:47am

Even i am rebuilding projects,the error is still there

Jochen Arndt 15-Sep-17 6:26am

Do you really need a debug build of that libraray?

If not, build that project as release only and use the release library version also with the debug builds of the other projects. That will not solve the problem but you can go on working on the other projects.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2017-09-18T23:56:00

Solution 1

Copy your original project to a new folder before trying the upgrade: then clean it to remove all intermediate files and do a full rebuild. Use "Build...Clean Solution", then delete the BIN and OBJ folders for each project in the solution and everything below them as well to be on the safe side. Then do a full Rebuild on the solution to see what happens. If you are referencing DLL files from other solutions as well, do the same there as well.

Posted 18-Sep-17 23:56pm

OriginalGriff

Comments

Naveen_vemuri 19-Sep-17 6:09am

I tried it for so many times but not getting resolved.when i turn of "Properties->Linker->debugging->generate debugging info" to NO it is running fine,but i need pdb file too.Is there any other way we can solve this?

RedDk 19-Sep-17 12:25pm

The .pdb file is the program debug data. This file is generated by the compiler/(linker(sp?)). There's a switch in the project properties (in C++ anyway; might not be there in C# ...) that forgoes output so presumeably no .pdb will make an appearance post rebuild.