Text only | Text with Images

The MASM Forum

General => The Workshop => Topic started by: jj2007 on March 05, 2023, 09:27:59 AM

Title: Symbols: pdb + ilk or embedded in the executable?
Post by: jj2007 on March 05, 2023, 09:27:59 AM
I get a stupid error message:
Code Select
*** Link SimpleEd.obj rsrc.res  using polink, sub WINDOWS /debug ***
Writing debug information
POLINK: warning: Unrecognized CodeView symbols version (4) in object 'tinf.lib(Tmp_File.obj)'; ignored.
Compacting CodeView information
*** SimpleEd.exe: 489984 bytes ***

So I wanted to find a way to strip these symbols from tinf.lib (built with Pelles C), but searching in link, lib, polink and polib didn't satisfy my desire. Then I also realised that I haven't seen pdb or ilk files for quite, i.e. my symbols are always embedded in the exe. Why is that? Is there any option that determines whether symbols are embedded or "outsourced" to pdb files?

Stupid questions, I know, but I hope somebody can help me.

P.S.: Funnily enough, SOF claims (https://stackoverflow.com/questions/45745228/windows-executables-with-complete-embedded-debug-symbols) "It is not possible to create an .exe or .dll that contains debug information. Debug information is always placed in a .obj or .pdb file."
Title: Re: Symbols: pdb + ilk or embedded in the executable?
Post by: HSE on March 05, 2023, 10:03:38 AM
There is a PellesC subforum!

Just erase "stupid" from text  :biggrin:
Title: Re: Symbols: pdb + ilk or embedded in the executable?
Post by: jj2007 on March 05, 2023, 12:05:50 PM
Quote from: HSE on March 05, 2023, 10:03:38 AM
There is a PellesC subforum!

I know, but that doesn't answer my question.
Title: Re: Symbols: pdb + ilk or embedded in the executable?
Post by: wjr on March 05, 2023, 04:25:34 PM
With POLINK the /debug option will include the debug information in the executable file, or the /DBG option (Project Options, Linker, Generate DBG file) creates a separate .dbg file with the debug information. As for the lib file, and in particular that Tmp_File.obj file, you could try a Pelles C build with the /Zd option (just COFF debug information) instead of /Zi.
Title: Re: Symbols: pdb + ilk or embedded in the executable?
Post by: TimoVJL on March 05, 2023, 07:03:17 PM
polink cw support is limited, as CodeView isn't documented well.
also version 11 use it's own debug format.
Title: Re: Symbols: pdb + ilk or embedded in the executable?
Post by: jj2007 on March 05, 2023, 10:41:26 PM
Thank you, Wayne and Timo. I've tried all combinations of options and linkers, and did not yet get what I want, i.e. no warning :sad:

Will keep trying...
Title: Re: Symbols: pdb + ilk or embedded in the executable?
Post by: wjr on March 06, 2023, 06:36:32 AM
To Compile the lib OBJ file, if you go to Project Options..., Compiler, Debug information: and set this to None and also on the toolbar select Release instead of Debug, this combination would appear to compile without the output of sections .debug$S and .debug$T which would contain CodeView or related Pelles C debug information.
Title: Re: Symbols: pdb + ilk or embedded in the executable?
Post by: jj2007 on March 06, 2023, 09:57:30 AM
Thanks again, Wayne - you gave me a good idea: to launch PoIde.exe instead of using my usual batch file :biggrin:

So with "verbose build" I managed to see the winning options:

\Masm32\PellesC\Bin\pocc.exe -Tx86-coff -std:C17 -Ot -Ob1 -fp:precise -W1 -Gz -Zl tinfBuildLib.c -FoTinf.obj
\Masm32\PellesC\Bin\polib.exe  -out:Tinf.lib Tinf.obj

Plus Options/Compiler/Code generation: Omit default library name in object files (otherwise it complains about missing crt.lib)

It works, and the lib is even a lot shorter :thumbsup:
Text only | Text with Images