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:

  1. Download and unzip “procdump.exe”.
  2. 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"
  3. ProcDump will ask you if you accept the license agreement; click the I Agree button.
  4. Logos 4 will launch (but no splash screen will be displayed); wait for it to open, which may take longer than normal.
  5. 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.
  6. Open Windows Explorer to the UNZIPPATH folder. There should be a file named Logos4.dmp.
  7. Zip up the Logos4.dmp file and email the zip file to your tech support contact.
  8. 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



Logos Bible Software Wiki

Welcome, Guest! (sign in)