Member Avatar for studentffm

Hi,

I have the following problem:
I have a program which uses NAG C library and when i compile it everything is fine, however when I want to start the program with debugging i have the following output:

'desktop.exe': Loaded 'C:\Users\Jorko\Desktop\test\projekt\desktop\Debug\desktop.exe', Symbols loaded.
'desktop.exe': Loaded 'C:\Windows\System32\ntdll.dll'
'desktop.exe': Loaded 'C:\Windows\System32\kernel32.dll'
'desktop.exe': Loaded 'C:\Program Files\NAG\CL08\cldll084zl\bin\CLDLL084Z_nag.dll', Binary was not built with debug information.
'desktop.exe': Loaded 'C:\Windows\System32\user32.dll'
'desktop.exe': Loaded 'C:\Windows\System32\gdi32.dll'
'desktop.exe': Loaded 'C:\Windows\System32\advapi32.dll'
'desktop.exe': Loaded 'C:\Windows\System32\rpcrt4.dll'
'desktop.exe': Loaded 'C:\Windows\System32\wsock32.dll'
'desktop.exe': Loaded 'C:\Windows\System32\ws2_32.dll'
'desktop.exe': Loaded 'C:\Windows\System32\msvcrt.dll'
'desktop.exe': Loaded 'C:\Windows\System32\nsi.dll'
'desktop.exe': Loaded 'C:\Windows\System32\IPHLPAPI.DLL'
'desktop.exe': Loaded 'C:\Windows\System32\dhcpcsvc.dll'
'desktop.exe': Loaded 'C:\Windows\System32\dnsapi.dll'
'desktop.exe': Loaded 'C:\Windows\System32\secur32.dll'
'desktop.exe': Loaded 'C:\Windows\System32\winnsi.dll'
'desktop.exe': Loaded 'C:\Windows\System32\dhcpcsvc6.dll'
'desktop.exe': Loaded 'C:\Program Files\NAG\CL08\cldll084zl\bin\matrix32.dll', Binary was not built with debug information.
'desktop.exe': Loaded 'C:\Windows\System32\winspool.drv'
'desktop.exe': Loaded 'C:\Windows\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.3053_none_d08d7bba442a9b36\msvcr80.dll'
'desktop.exe': Loaded 'C:\Windows\winsxs\x86_microsoft.vc90.debugcrt_1fc8b3b9a1e18e3b_9.0.30729.1_none_bb1f6aa1308c35eb\msvcp90d.dll'
'desktop.exe': Loaded 'C:\Windows\winsxs\x86_microsoft.vc90.debugcrt_1fc8b3b9a1e18e3b_9.0.30729.1_none_bb1f6aa1308c35eb\msvcr90d.dll'
'desktop.exe': Loaded 'C:\Windows\System32\imm32.dll'
'desktop.exe': Loaded 'C:\Windows\System32\msctf.dll'
'desktop.exe': Loaded 'C:\Windows\System32\lpk.dll'
'desktop.exe': Loaded 'C:\Windows\System32\usp10.dll'
'desktop.exe': Loaded 'C:\Program Files\Google\Google Desktop Search\GoogleDesktopNetwork3.dll'
'desktop.exe': Loaded 'C:\Windows\System32\ntmarta.dll'
'desktop.exe': Loaded 'C:\Windows\System32\Wldap32.dll'
'desktop.exe': Loaded 'C:\Windows\System32\psapi.dll'
'desktop.exe': Loaded 'C:\Windows\System32\samlib.dll'
'desktop.exe': Loaded 'C:\Windows\System32\ole32.dll'
'desktop.exe': Unloaded 'C:\Program Files\Google\Google Desktop Search\GoogleDesktopNetwork3.dll'
'desktop.exe': Loaded 'C:\Program Files\Kaspersky Lab\Kaspersky Anti-Virus 2010\mzvkbd3.dll'
'desktop.exe': Loaded 'C:\Windows\System32\acaptuser32.dll', Binary was not built with debug information.
'desktop.exe': Unloaded 'C:\Windows\System32\acaptuser32.dll'
'desktop.exe': Loaded 'C:\Windows\System32\uxtheme.dll'
'desktop.exe': Loaded 'C:\Program Files\IDM\Desktop SMS\oehook.dll', Binary was not built with debug information.
'desktop.exe': Loaded 'C:\Windows\System32\clbcatq.dll'
'desktop.exe': Loaded 'C:\Windows\System32\oleaut32.dll'
'desktop.exe': Unloaded 'C:\Program Files\Kaspersky Lab\Kaspersky Anti-Virus 2010\mzvkbd3.dll'
The thread 'Win32 Thread' (0x14e0) has exited with code 0 (0x0).
The program '[4184] desktop.exe: Native' has exited with code 3 (0x3).

Can you help me to solve the problems in the bold text. I am using VC++ and I am sure that debugging is configured properly.

10x for any assistance

  • 2 Contributors
  • 3 Replies
  • 273 Views
  • 8 Hours Discussion Span
  • Latest Post Latest Post by Ancient Dragon

Dani AI

Generated

Short answer: Visual Studio is simply telling you that those NAG DLLs were built without debug symbols, so the debugger can’t load their PDBs and you won’t be able to step into their source or see their local variables. That’s normal for third‑party release builds and is not a virus. As suggested, MFC can sometimes introduce symbol-loading oddities, but this message itself just means “no debug info available” for those modules.

Concrete steps to diagnose and (if possible) fix it:

  • Open Debug -> Windows -> Modules, find the NAG DLLs and check the Symbol Status column. Right‑click a module and use Load Symbols From -> File... to point to a matching .pdb if you have one.
  • Configure symbol paths in Tools -> Options -> Debugging -> Symbols (add a local folder or network location where vendor PDBs live). Visual Studio will tell you if the PDB GUID/timestamp does not match the DLL.
  • If no PDB exists, stepping into source won’t work; you can still use the Disassembly window (Debug -> Windows -> Disassembly) and the Call Stack to get addresses and instruction-level context.

If you have (or can build) the library source:

  • Build with debug info enabled: use the compiler flag /Zi (or /Z7) and link with /DEBUG so a .pdb is produced and shipped with the DLL. The PDB must match the DLL exactly.

If you do not have source:

  • Ask NAG for a debug build or a symbol package (many vendors provide separate debug libs or symbol-only PDBs). If that’s unavailable, focus debugging on your own code: set breakpoints before/after the NAG call, enable first‑chance exceptions, or disable “Just My Code” so the call stack shows external frames (addresses only).

Extra tips: confirm the exact DLL being loaded (use Process Explorer or Dependency Walker), watch for CRT/runtime mismatches between your app and the third‑party DLL, and use the Modules window’s symbol load details to understand why symbols failed to load.

Recommended Answers

All 3 Replies

Member Avatar for Ancient Dragon

Are those your DLLs? Or do you have the source code so that you can recompile them with debug information?

Member Avatar for studentffm

Are those your DLLs? Or do you have the source code so that you can recompile them with debug information?

Hi,

do you mean the dlls in the bold text? I have the ddls they are from the external library which is installed but somehow the program cannot be started with debug information

Member Avatar for Ancient Dragon

The only time I've seen that to be a problem is with MFC programs. Otherwise you should be able to debug your own code without a problem.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.