ProcDump
ProcDump
Wiki: TOC, VTOC, Home Forum: Home, Gen, L4, Mac4
If instructed to by Tech Support, please follow these instructions to create a crash dump of Logos 4:
- Download and unzip “procdump.exe”.
- Click “Download ProcDump” at http://technet.microsoft.com/en-us/sysinternals/dd996900.aspx
- Unzip the contents of that file to a new folder on your hard disk.
- Open a command prompt. In that command prompt, enter the following commands (replacing UNZIPPATH with the full path to where you unzipped the file in step 1):
cd UNZIPPATH
- Logos4:
procdump -e -g -x . "%LOCALAPPDATA%\Logos4\System\Logos4.exe"
- Logos5:
procdump -e -g -x . "%LOCALAPPDATA%\Logos5\System\Logos.exe"
- ProcDump will ask you if you accept the license agreement; click the I Agree button.
- Logos 4 will launch (but no splash screen will be displayed); wait for it to open, which may take longer than normal.
- Perform the action that caused the crash. When the crash happens, the program will seem to hang while debugging information is collected. If prompted to close Logos 4, close it.
- Open Windows Explorer to the UNZIPPATH folder. There should be a file named
Logos4.dmp
. - Zip up the
Logos4.dmp
file and email the zip file to your tech support contact. - Once you have confirmed receipt of the crash dump, you can delete the
Logos4.dmp
file to save disk space.
Creating a Hang Dump
The instructions are the same as above, except in step 2, run
- Logos4:
procdump -h -x "%LOCALAPPDATA%\Logos4\System\Logos4.exe" Logos4.dmp
- Logos5:
procdump -h -x "%LOCALAPPDATA%\Logos5\System\Logos.exe" Logos5.dmp
Collecting Diagnostics for the Indexer
If the Logos 4 Indexer is hanging or crashing, use the same instructions as above, but change Logos4.exe
in the commands to Logos4Indexer.exe
Was this article helpful?
Be the first one to vote!
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service
Loading