c++ - Debugging dump file Call Stack has not much info -


our customer reported "microsoft visual c++ runtime library: runtime error!" received dump file (.dmp) them. debugged using visual studio 2013 call stack has 5 lines:

[external code] myprogram.exe!afxinternalpumpmessage() line 153 myprogram.exe!afxwinmain(hinstance__ * hinstance, hinstance__ * hprevinstance, char * lpcmdline, int ncmdshow) line 47 myprogram.exe!__tmaincrtstartup() line 263 [external code] 

all lines trace mfc code, , nothing our source code.

what "[external code]" referring there?

am doing wrong? thank you!

actually, found out can expand [external code] , becomes this:

user32.dll!_ntusergetmessage@16()    user32.dll!_getmessagea@16()     myprogram.exe!afxinternalpumpmessage() line 153 myprogram.exe!afxwinmain(hinstance__ * hinstance, hinstance__ * hprevinstance, char * lpcmdline, int ncmdshow) line 47 myprogram.exe!__tmaincrtstartup() line 263 kernel32.dll!@basethreadinitthunk@12()   ntdll.dll!___rtluserthreadstart@8()  ntdll.dll!__rtluserthreadstart@8()   

but still nothing source code.

did try windbg.exe? @blacktempel said, need .pdb files build. means every time deliver code customers, have keep .pdb files(at least) debugging.

you can reference link below, https://msdn.microsoft.com/en-us/library/windows/hardware/ff538042(v=vs.85).aspx


Comments

Popular posts from this blog

dns - How To Use Custom Nameserver On Free Cloudflare? -

python - Pygame screen.blit not working -

c# - Web API response xml language -