Author Topic: How to get more information about the error  (Read 3504 times)

Offline alex

  • Developer
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2224
  • Karma: +37/-3
    • HippoEDIT
How to get more information about the error
« on: January 02, 2009, 12:35:13 PM »
In some cases when it is not possible to easy reproduce crash/hanging or it is unregular or happens only on your machine, it is possible to get more information about the error using debug information for HippoEDIT (HE) and special tools.

So what to do if you are willing to help, but dont know how.

Get HE installation with debug symbols. It can be found here: - 9 Mb (replace 140 to actual version, fex 1.44 -> 144 or 1.54 -> 145 or 1.50 -> 150). If file does not exist on server or you coud not reproduce the error with this installation (it is not always up to date), then ask on here to update it.

There are two ways to get call stack of the error.

Process Explorer. Easy way, but less informative
  • Download Process Explorer from here (very good tool, like extended Task Manager).
  • Unpack, start.
  • Run HE from installation with debug symbols and try to reproduce the crash.
  • After you get crash message box, go to Process Explorer, find process Hippoedit.exe, double click on it.
  • In "Properties" window find tab "Threads", select thread with Hippoedit.exe in name and click on button Stack.
  • Copy stack trace and send it to us. Probably it would not be corrupted and can help us to find starting point for problem...

Microsoft Debugger. Harder way, but more informative
You can use free Microsoft Debugger (WinDBG) to create special dump with information about the call stack of the error.
  • Install Debugging tools from Microsoft website (very fast, requires no validation etc) - 17 Mb on the machine where the HippoEDIT has to be analyzed.
  • Download this file into the Debugging Tools installation folder (C:\Program Files\Debugging Tools for Windows).
  • Set environment variable to load windows symbols (explanation how to set an environment variable can be found here):
    _NT_SYMBOL_PATH= symsrv*symsrv.dll*c:\pdbs*
  • Then start HippoEDIT and reproduce the scenario or work with HippoEDIT if not reproducible.
  • BEFORE the exception occurs you have to do the following:
  • Enter in the Start/Run dialog "cmd.exe"
  • Then in the command prompt run the following command:
    cd "C:\Program Files\Debugging Tools for Windows (x86)"
    adplus.vbs -c adplus_cfg.txt
  • You will get the following popup:

    "WScript is currently your default script processor... Would you like to register CScript..."
    => choose "Yes"

    "Successfully registered CStript.exe ... The change back type 'wscript.exe //h:wscript" in a command shell"
    => do this later after finishing the analysis

    "AdPlus is now running in CRASH mode... please check the ... directory"
    => choose "OK"
  • Now reproduce the crash. Check inside this directory whether a "Crash*" sub directory has been created:
    C:\program Files\Debugging Tools for Windows (x86)

    ...for Windows\Crash_Mode__Date_01-17-2008__Time_11-11-1515

    Take directory with latest time.
  • Then please send us the zipped directory's content with description how to reproduce the error if possible.
  • Copy of this description together with attached file can be downloaded here.
  • Files to be sent is simple log text files and contain no confidential information.
« Last Edit: March 06, 2010, 01:17:59 AM by alex »