Difference between revisions of "Inspecting mini dump files"
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=Inspecting= | =Inspecting= | ||
| − | *On | + | *On the PC with VS2019: go to '''\\192.168.0.1\FiP Installations\FIELDPRO_V8x\FIELDPRO V8x xxx.xx.xxxx''' and then copy '''Sources.zip''' |
| − | *Extract '''Sources.zip''' | + | *Extract '''Sources.zip''' to any folder ('''d:\v8_crash'''), subst this folder to the Y drive: |
subst y: /d | subst y: /d | ||
subst y: d:\v8_crash | subst y: d:\v8_crash | ||
| Line 7: | Line 7: | ||
*Open VS2019 (Continue without code), Open\File and select *mini_dump.dmp | *Open VS2019 (Continue without code), Open\File and select *mini_dump.dmp | ||
*Set symbol paths: | *Set symbol paths: | ||
| − | for FiP: | + | for '''FiP''': |
Y:\Release.exe | Y:\Release.exe | ||
Y:\Release.lib | Y:\Release.lib | ||
| − | for Modules: | + | for '''Modules''': |
Y:\Modules.32\Release.exe | Y:\Modules.32\Release.exe | ||
Y:\Modules.32\Release.lib | Y:\Modules.32\Release.lib | ||
| Line 18: | Line 18: | ||
Debug Managed Only | Debug Managed Only | ||
| + | =Testing= | ||
| + | In some cases it is required to test the application (PHX) in critical conditions (after the crash). | ||
| + | To initiate the program exception failure: | ||
| + | #Close all screens | ||
| + | #Type "give me the crash" | ||
=Inspecting Old= | =Inspecting Old= | ||
| Line 31: | Line 36: | ||
and then in View menu open '''Show Stack''' (and then Source args) and '''Locals''' | and then in View menu open '''Show Stack''' (and then Source args) and '''Locals''' | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
=Tags= | =Tags= | ||
Acton, dump, crash, log, inspect, test, debug. | Acton, dump, crash, log, inspect, test, debug. | ||
Latest revision as of 06:52, 28 June 2022
Contents
Inspecting
- On the PC with VS2019: go to \\192.168.0.1\FiP Installations\FIELDPRO_V8x\FIELDPRO V8x xxx.xx.xxxx and then copy Sources.zip
- Extract Sources.zip to any folder (d:\v8_crash), subst this folder to the Y drive:
subst y: /d subst y: d:\v8_crash
- Extract FIP_SYSTEM_LOG.err\copy *mini_dump.dmp to folder: d:\v8_crash
- Open VS2019 (Continue without code), Open\File and select *mini_dump.dmp
- Set symbol paths:
for FiP:
Y:\Release.exe Y:\Release.lib
for Modules:
Y:\Modules.32\Release.exe Y:\Modules.32\Release.lib
- And then press:
Debug with Native Only Debug Mixed Debug Managed Only
Testing
In some cases it is required to test the application (PHX) in critical conditions (after the crash). To initiate the program exception failure:
- Close all screens
- Type "give me the crash"
Inspecting Old
- Extract FIP_SYSTEM_LOG.err to folder: E:\FiP_Versions\
- Look at file E:\FiP_Versions\version.info and find FiP version
- Copy correct fip version from E:\FiP_Versions\v8d\{FiP version} to E:\FiP_Versions\dump_check
- Copy mini_dump.dmp to E:\FiP_Versions\
- Run dumpcheck.bat
after run commands in cmd: go to exception: .ecxr show stack: k
and then in View menu open Show Stack (and then Source args) and Locals
Tags
Acton, dump, crash, log, inspect, test, debug.
