News:

Masm32 SDK description, downloads and other helpful links
Message to All Guests

Main Menu

fatal error LNK1103

Started by ragdog, September 14, 2015, 08:56:42 PM

Previous topic - Next topic

ragdog

Hello

I very confused and have no idea
I use Visual Studio 2008 sp1 and build a lib.

Now bind it in my Masm32 project but i switch to debug build have i by linking this error.

Quote"LINK : fatal error LNK1000: unknown error; consult documentation for technical support options"

Ok i have think i make a debug build of this Lib and try to bind it again in my project now have i this error

QuoteMytest.lib(Funktion1.obj) : fatal error LNK1103: debugging information corrupt; recompile module

In Release mode works all fine.

Any idea?

Regards,

jj2007

Some assembler/linker combinations simply don't work properly. Try:

- first, to delete any obj, pdb, ilk files, then recompile
- if that doesn't help, assemble with JWasm and link with the last link.exe

ragdog

#2
I think i have this error i have make a lib debug build  with Vs2008

Cpp Linker version  (Version 9.00.30729.01)

Masm Linker Version 5.12.8078

Now have i compile my masm project with this linker and voila it works.

I think the old linker from masm32 pack have problem to create debug files (pdb) if a lib created with a later version of linker

Curious :icon_exclaim:


TWell

Maybe newer cl.exe and ml.exe generate debug-info than can handle with newer linker only.
Only cl.exe have /Z7 enable old-style debug info.

Perhaps polink.exe version 8 can handle that debug-info too.

ragdog

QuoteOnly cl.exe have /Z7 enable old-style debug info.

With this option have i this same problem
QuoteMytest.lib(Funktion1.obj) : fatal error LNK1103: debugging information corrupt; recompile module

hutch--

Always use a matching linker for the style of debugging you want to use.  :eusa_naughty:

ragdog

Hello Hutch

Why  :eusa_naughty: ??

My CL settings is
cl.exe /nologo  /W3 /ZI /Zi /D_DEBUG   /I"C:\Program Files\Microsoft SDKs\Windows\v6.0A\include" /I"C:\Program Files\Microsoft Visual Studio 9.0\VC\include" /c ..\source\Test.c /Foobj\Debug\source\test.obj

Any a good solution?

hutch--

Debugging formats have changed over time. If you want to use and old linker, use the old debugger that matches it.

ragdog

Its right Hutch

But i wonder me in other projects have i libs build with masm or with visual studio from other Peoples
it works i switch do debug build without to make a libaray in debug build.

ragdog

Thank you all

I have test it with Vs 2010 express its same but with Vc 2003 toolkit works fine
or use a newer linker.

regards,