Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
29276 Discussions

Console app in debug : module built without symbols

alexandre_c_1
Beginner
6,911 Views

Hi,

I am trying to built a console app in debug config. The exe is triggering a breakpoint and I get the message saying that the module libifcoremdd.dll was built without symbols

'ifort.exe' (Win32): Loaded '\\hqfs2\pengen\2013\UVS\Version\V1\ifort\Debug\ifort.exe'. Symbols loaded.

'ifort.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ntdll.dll'. Symbols loaded.
'ifort.exe' (Win32): Loaded 'C:\Windows\SysWOW64\kernel32.dll'. Symbols loaded.
'ifort.exe' (Win32): Loaded 'C:\Windows\SysWOW64\KernelBase.dll'. Symbols loaded.
'ifort.exe' (Win32): Loaded 'C:\Windows\SysWOW64\sysfer.dll'. Cannot find or open the PDB file.
'ifort.exe' (Win32): Loaded 'C:\Program Files (x86)\Intel\Composer XE 2015\redist\ia32\compiler\libifcoremdd.dll'. Module was built without symbols.
'ifort.exe' (Win32): Loaded 'C:\Program Files (x86)\Intel\Composer XE 2015\redist\ia32\compiler\libmmd.dll'. Symbols loaded.
'ifort.exe' (Win32): Loaded 'C:\Windows\SysWOW64\imagehlp.dll'. Symbols loaded.
'ifort.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msvcrt.dll'. Symbols loaded.
'ifort.exe' (Win32): Loaded 'C:\Windows\SysWOW64\advapi32.dll'. Symbols loaded.
'ifort.exe' (Win32): Loaded 'C:\Windows\SysWOW64\sechost.dll'. Symbols loaded.
'ifort.exe' (Win32): Loaded 'C:\Windows\SysWOW64\rpcrt4.dll'. Symbols loaded.
'ifort.exe' (Win32): Loaded 'C:\Windows\SysWOW64\sspicli.dll'. Symbols loaded.
'ifort.exe' (Win32): Loaded 'C:\Windows\SysWOW64\cryptbase.dll'. Symbols loaded.
'ifort.exe' (Win32): Loaded 'C:\Program Files (x86)\Intel\Composer XE 2015\redist\ia32\compiler\libifportmd.dll'. Module was built without symbols.
'ifort.exe' (Win32): Loaded 'C:\Windows\SysWOW64\user32.dll'. Symbols loaded.
'ifort.exe' (Win32): Loaded 'C:\Windows\SysWOW64\gdi32.dll'. Symbols loaded.
'ifort.exe' (Win32): Loaded 'C:\Windows\SysWOW64\lpk.dll'. Symbols loaded.
'ifort.exe' (Win32): Loaded 'C:\Windows\SysWOW64\usp10.dll'. Symbols loaded.
'ifort.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msvcr110d.dll'. Symbols loaded.
'ifort.exe' (Win32): Loaded 'C:\Windows\SysWOW64\imm32.dll'. Symbols loaded.
'ifort.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msctf.dll'. Symbols loaded.
'ifort.exe' (Win32): Loaded 'C:\Windows\SysWOW64\dbghelp.dll'. Symbols loaded.

 

I am stuck there. Note: When I build in release configuration I do not get the message. 

Is there any symbol file for libifcoremdd ?

How can I go pass that ?

Thank you

0 Kudos
3 Replies
mecej4
Honored Contributor III
6,911 Views

You can ignore the warning about the runtime DLL not containing symbols, except when you want to debug the runtime itself. Warnings of this type are normal. You get the warning only when you use a debug configuration and one of the libraries linked does not contain debug information. 

0 Kudos
Steven_L_Intel1
Employee
6,911 Views

You don't say how you are "stuck", but I think I know what you refer to - Visual Studio doesn't let you do anything unless you can provide a path to the Run-Time Library DLL symbols, and we don't provide them. This is new behavior for VS and it's under investigation. As a workaround,  change the Libraries > Use Run-Time Libraries setting to "Multithreaded" instead of "Multithread DLL". It's curious that it doesn't affect all programs.

0 Kudos
alexandre_c_1
Beginner
6,911 Views

It seems like the change of "Run-Time Libraries setting to "Multithreaded" instead of "Multithread DLL" have worked as a workaround the symbol problem for the libifcoremdd.dll' and the libifportmd.dll. Thank you steve.

 

 

0 Kudos
Reply