WinDebug 除錯工具-0
阿新 • • 發佈:2018-12-30
Loading Dump File [F:\Debug分析除錯工具\SysinternalsSuite\ProDebug.exe_180712_171559.dmp]
User Mini Dump File with Full Memory: Only application data is available
Comment: '
*** procdump64.exe -ma -t 9872
*** Unhandled exception: C0000094.INT_DIVIDE_BY_ZERO'
************* Path validation summary **************
Response Time (ms) Location
OK C:\Users\02258.YANMADE\Documents\Visual Studio 2013\Projects\ProDebug\Debug
Symbol search path is: C:\Users\02258.YANMADE\Documents\Visual Studio 2013\Projects\ProDebug\Debug
Executable search path is:
Windows 7 Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: SingleUserTS
6.1.7601.17965 (win7sp1_gdr.121004-0333)
Machine Name:
Debug session time: Thu Jul 12 17:16:00.000 2018 (UTC + 8:00)
System Uptime: 1 days 1:04:59.712
Process Uptime: 0 days 0:00:41.000
...........
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -
************* Symbol Loading Error Summary **************
Module name Error
ntdll PDB not found : c:\users\02258.yanmade\documents\visual studio 2013\projects\prodebug\debug\symbols\dll\ntdll.pdb
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(2690.27e4): Integer divide-by-zero - code c0000094 (first/second chance not available)
*** ERROR: Symbol file could not be found. Defaulted to export symbols for wow64.dll -
wow64!Wow64LdrpInitialize+0x8d5:
00000000`7546cb49 654c8b1c2530000000 mov r11,qword ptr gs:[30h] gs:00000000`00000030=????????????????
0:000> .load wow64exts
0:000> !sw
Switched to Guest (WoW) mode
*** WARNING: Unable to verify checksum for ProDebug.exe
*** ERROR: Module load completed but symbols could not be loaded for ProDebug.exe
*** ERROR: Symbol file could not be found. Defaulted to export symbols for kernel32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -
************* Path validation summary **************
Response Time (ms) Location
OK C:\Users\02258.YANMADE\Documents\Visual Studio 2013\Projects\ProDebug\Debug
0:000:x86> .reload
...........
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -
*** WARNING: Unable to verify checksum for ProDebug.exe
*** ERROR: Module load completed but symbols could not be loaded for ProDebug.exe
************* Symbol Loading Error Summary **************
Module name Error
ntdll PDB not found : c:\users\02258.yanmade\documents\visual studio 2013\projects\prodebug\debug\symbols\dll\ntdll.pdb
ProDebug PDB not found : c:\users\02258.yanmade\documents\visual studio 2013\projects\prodebug\debug\symbols\exe\ProDebug.pdb
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*** ERROR: Symbol file could not be found. Defaulted to export symbols for kernel32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -
0:000:x86> .reload -i
.*** WARNING: Unable to verify checksum for ProDebug.exe
.*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -
.*** ERROR: Symbol file could not be found. Defaulted to export symbols for wow64.dll -
.*** ERROR: Symbol file could not be found. Defaulted to export symbols for wow64win.dll -
.*** ERROR: Symbol file could not be found. Defaulted to export symbols for wow64cpu.dll -
.*** WARNING: Unable to verify checksum for ProDebug.exe
.*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -
.*** ERROR: Symbol file could not be found. Defaulted to export symbols for kernel32.dll -
.*** ERROR: Symbol file could not be found. Defaulted to export symbols for KERNELBASE.dll -
.*** ERROR: Symbol file could not be found. Defaulted to export symbols for MSVCP120D.dll -
.*** ERROR: Symbol file could not be found. Defaulted to export symbols for MSVCR120D.dll -
************* Symbol Loading Error Summary **************
Module name Error
ntdll PDB not found : c:\users\02258.yanmade\documents\visual studio 2013\projects\prodebug\debug\symbols\dll\ntdll.pdb
wow64 PDB not found : c:\users\02258.yanmade\documents\visual studio 2013\projects\prodebug\debug\symbols\dll\wow64.pdb
wow64win PDB not found : c:\users\02258.yanmade\documents\visual studio 2013\projects\prodebug\debug\symbols\dll\wow64win.pdb
wow64cpu PDB not found : c:\users\02258.yanmade\documents\visual studio 2013\projects\prodebug\debug\symbols\dll\wow64cpu.pdb
ntdll PDB not found : c:\users\02258.yanmade\documents\visual studio 2013\projects\prodebug\debug\symbols\dll\wntdll.pdb
kernel32 PDB not found : c:\users\02258.yanmade\documents\visual studio 2013\projects\prodebug\debug\symbols\dll\wkernel32.pdb
KERNELBASE PDB not found : c:\users\02258.yanmade\documents\visual studio 2013\projects\prodebug\debug\symbols\dll\wkernelbase.pdb
MSVCP120D PDB not found : c:\users\02258.yanmade\documents\visual studio 2013\projects\prodebug\debug\symbols\dll\msvcp120d.i386.pdb
MSVCR120D PDB not found : c:\users\02258.yanmade\documents\visual studio 2013\projects\prodebug\debug\symbols\dll\msvcr120d.i386.pdb
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
User Mini Dump File with Full Memory: Only application data is available
Comment: '
*** procdump64.exe -ma -t 9872
*** Unhandled exception: C0000094.INT_DIVIDE_BY_ZERO'
************* Path validation summary **************
Response Time (ms) Location
OK C:\Users\02258.YANMADE\Documents\Visual Studio 2013\Projects\ProDebug\Debug
Symbol search path is: C:\Users\02258.YANMADE\Documents\Visual Studio 2013\Projects\ProDebug\Debug
Executable search path is:
Windows 7 Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: SingleUserTS
6.1.7601.17965 (win7sp1_gdr.121004-0333)
Machine Name:
Debug session time: Thu Jul 12 17:16:00.000 2018 (UTC + 8:00)
System Uptime: 1 days 1:04:59.712
Process Uptime: 0 days 0:00:41.000
...........
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -
************* Symbol Loading Error Summary **************
Module name Error
ntdll PDB not found : c:\users\02258.yanmade\documents\visual studio 2013\projects\prodebug\debug\symbols\dll\ntdll.pdb
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(2690.27e4): Integer divide-by-zero - code c0000094 (first/second chance not available)
*** ERROR: Symbol file could not be found. Defaulted to export symbols for wow64.dll -
wow64!Wow64LdrpInitialize+0x8d5:
00000000`7546cb49 654c8b1c2530000000 mov r11,qword ptr gs:[30h] gs:00000000`00000030=????????????????
0:000> .load wow64exts
0:000> !sw
Switched to Guest (WoW) mode
*** WARNING: Unable to verify checksum for ProDebug.exe
*** ERROR: Module load completed but symbols could not be loaded for ProDebug.exe
*** ERROR: Symbol file could not be found. Defaulted to export symbols for kernel32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -
************* Path validation summary **************
Response Time (ms) Location
OK C:\Users\02258.YANMADE\Documents\Visual Studio 2013\Projects\ProDebug\Debug
0:000:x86> .reload
...........
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -
*** WARNING: Unable to verify checksum for ProDebug.exe
*** ERROR: Module load completed but symbols could not be loaded for ProDebug.exe
************* Symbol Loading Error Summary **************
Module name Error
ntdll PDB not found : c:\users\02258.yanmade\documents\visual studio 2013\projects\prodebug\debug\symbols\dll\ntdll.pdb
ProDebug PDB not found : c:\users\02258.yanmade\documents\visual studio 2013\projects\prodebug\debug\symbols\exe\ProDebug.pdb
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*** ERROR: Symbol file could not be found. Defaulted to export symbols for kernel32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -
0:000:x86> .reload -i
.*** WARNING: Unable to verify checksum for ProDebug.exe
.*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -
.*** ERROR: Symbol file could not be found. Defaulted to export symbols for wow64.dll -
.*** ERROR: Symbol file could not be found. Defaulted to export symbols for wow64win.dll -
.*** ERROR: Symbol file could not be found. Defaulted to export symbols for wow64cpu.dll -
.*** WARNING: Unable to verify checksum for ProDebug.exe
.*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -
.*** ERROR: Symbol file could not be found. Defaulted to export symbols for kernel32.dll -
.*** ERROR: Symbol file could not be found. Defaulted to export symbols for KERNELBASE.dll -
.*** ERROR: Symbol file could not be found. Defaulted to export symbols for MSVCP120D.dll -
.*** ERROR: Symbol file could not be found. Defaulted to export symbols for MSVCR120D.dll -
************* Symbol Loading Error Summary **************
Module name Error
ntdll PDB not found : c:\users\02258.yanmade\documents\visual studio 2013\projects\prodebug\debug\symbols\dll\ntdll.pdb
wow64 PDB not found : c:\users\02258.yanmade\documents\visual studio 2013\projects\prodebug\debug\symbols\dll\wow64.pdb
wow64win PDB not found : c:\users\02258.yanmade\documents\visual studio 2013\projects\prodebug\debug\symbols\dll\wow64win.pdb
wow64cpu PDB not found : c:\users\02258.yanmade\documents\visual studio 2013\projects\prodebug\debug\symbols\dll\wow64cpu.pdb
ntdll PDB not found : c:\users\02258.yanmade\documents\visual studio 2013\projects\prodebug\debug\symbols\dll\wntdll.pdb
kernel32 PDB not found : c:\users\02258.yanmade\documents\visual studio 2013\projects\prodebug\debug\symbols\dll\wkernel32.pdb
KERNELBASE PDB not found : c:\users\02258.yanmade\documents\visual studio 2013\projects\prodebug\debug\symbols\dll\wkernelbase.pdb
MSVCP120D PDB not found : c:\users\02258.yanmade\documents\visual studio 2013\projects\prodebug\debug\symbols\dll\msvcp120d.i386.pdb
MSVCR120D PDB not found : c:\users\02258.yanmade\documents\visual studio 2013\projects\prodebug\debug\symbols\dll\msvcr120d.i386.pdb
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.