Click here to Skip to main content
15,037,928 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
I am debugging my project under visual studio 2013 c++ also configured all Microsoft symbol server. Getting error
.../\SysWOW64\sysfer.dll'. Cannot find or open the PDB file.

...\...\20160125.011\UMEngx86.dll'. Cannot find or open the PDB file.

Rest of my .pdb file for .dll loaded successfully. Yes, i have SEP (semantic end point protection) antivirus running in my system which i can not disable or stop. I am using windows-7 x64 machine.

Screen-shot of part of my project debugging output (only where i have a problem in output).(see line no-2 and 3)
<pre lang="c++"><pre lang="C#">32): Loaded 'C:\Windows\SysWOW64\KernelBase.dll'. Symbols loaded.

'Demo.exe' (Win32): Loaded 'C:\Windows\SysWOW64\sysfer.dll'. Cannot find or open the PDB file.

'Demo.exe' (Win32): Loaded 'C:\ProgramData\Symantec\Symantec Endpoint Protection\12.1.4112.4156.105\Data\Definitions\BASHDefs\20160125.011\UMEngx86.dll'. Cannot find or open the PDB file.

'Demo.exe' (Win32): Loaded 'C:\DLCT_kula\DLCT_CODE\release\log4cplus.dll'. Module was built without symbols.

'Demo.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ws2_32.dll'. Symbols loaded.

Please any one could suggest any idea how i can fix this issue. Thanks in advance.

What I have tried:

I tried to debug my code in visual studio 2013 c++ getting a error .pdb not found for UMEngx86.dll.
Updated 15-Jan-19 16:17pm

This is not an error but an informational message.

The PDB files are providing the debug information (symbol names) when stepping through code inside the corresponding module. Because you will probably want to debug your code and not third party modules, you can ignore the message.
Kulamani Sethi 15-Feb-16 4:49am
@Jochen, you are right! i can ignore message from third party module. When i am debugging my code throw a exception from heap manager. For that reason i need to understand each module debugging process. Here is my VC++ call stack track report;
Exception throw at Line 70;

ntdll.dll!_RtlpBreakPointHeap@4() Unknown
ntdll.dll!_RtlpCheckBusyBlockTail@8() Unknown
ntdll.dll!_RtlpValidateHeapEntry@12() Unknown
ntdll.dll!_RtlDebugFreeHeap@12() Unknown
ntdll.dll!@RtlpFreeHeap@16() Unknown
ntdll.dll!_RtlFreeHeap@12() Unknown
kernel32.dll!_HeapFree@12() Unknown
Demo.exe!free(void * pBlock=0x00698da0) Line 51 C
> Demo.exe!encryption(char * buffer=0x0065eaf8) Line 70 C++
Demo.exe!processRetrieveContentWS() Line 89 C++
Demo.exe!retrieveContentWS(void * dummy=0x00000000) Line 56 C++
Demo.exe!_callthreadstart() Line 255 C
Demo.exe!_threadstart(void * ptd) Line 237 C
kernel32.dll!@BaseThreadInitThunk@12() Unknown
ntdll.dll!___RtlUserThreadStart@8() Unknown
ntdll.dll!__RtlUserThreadStart@8() Unknown

If you have any idea please do replay.
Jochen Arndt 15-Feb-16 5:24am
Don't bother with binary code from other modules. Try to identify the error in your program.

The above call stacks show that there may be a heap curruption when freeing the pBlock memory. A common reason is that you write to another allocated buffer out of bounds (e.g. the one in memory before pBlock when using an index at or a little bit above it's size).

Overall you should try to locate the error yourself because finding it requires inspecting all involved source code lines which is rather impractical for an online forum like CodeProject.

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

CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900