Crash reports

From Miranda NG
Revision as of 18:39, 5 February 2013 by RMN (talk | contribs) (links specified)
Jump to navigation Jump to search
  • BE (Page should be fixed.)
  • CS (Page should be fixed.)
  • DE
  • EN
  • PL (Page should be fixed.)
  • RU

Reports generated by CrashDumper by default are insufficient and of little use. To create a useful crash report you need to do the following:

  • Install the CrashDumper plugin (see the plugin card for download links)
  • Update manually all the plugins from the corresponding source (stable/latest). This is not the case to rely upon the PluginUpdater.
  • Download debug symbols archive miranda-ng-debug-symbols*.7z from the corresponding source (stable x32 stable x64 / latest x32 latest x64)
  • Extract .pdb files named identically with your plugins from the archive to main Miranda NG folder. Do not extract anything to Plugins folder.
  • Try to reproduce the crash.
Examples
  1. Wrong: http://pastie.org/5456564. Some debug symbols are missing which is denoted by lines "(filename not available) (0): (function-name not available)" with Miranda core/plugins names (Lines with USER32, ntdll, kernel32, etc. don't matter).
  2. Right: http://pastie.org/5456572. All debug symbols are in place, no lines "(filename not available) (0): (function-name not available)" with Miranda core/plugins names.

Tips and tricks

  • Upload your crash reports to pastebin.com or pastie.org.
  • Each time you update the plugins you have to re-download the debug symbols.