Crash reports: Difference between revisions

From Miranda NG
Jump to navigation Jump to search
m (+See also)
No edit summary
Line 6: Line 6:


== Install CrashDumper ==
== Install CrashDumper ==
Install the appropriate version of {{Plugin|en|CrashDumper}} plugin (see plugin card for download links). Also, you can download and install it automatically using {{Plugin|en|PluginUpdater}}: go to ''Main Menu → Show full plugin list'', select <tt>CrashDumper</tt> and click ''Download'' button.
Install the appropriate version of {{Plugin|en|CrashDumper}} plugin. You can do this manually (download links are found in the plugin card on its page) or automatically using {{Plugin|en|PluginUpdater}}: go to ''Main Menu → Show full plugin list'', select <tt>CrashDumper</tt> and click ''Download'' button.




== Update your plugins and debug symbols ==
== Update plugins and debug symbols ==
All your plugins and Miranda core files must be of the latest version. Also, the debug symbols (PDB files) must be of the same compilation as the plugins, so it is necessary to update them too (or install if you don't have any).
All your plugins and Miranda core files must be of the latest version. Also, the debug symbols (<tt>PDB</tt> files) must be of the same compilation as the plugins, so it is necessary to update them too (or install if you don't have any).
{{Message|message=All reported issues are checked and fixed on trunk, that's why creating crash reports using only the latest [[development version]] of Miranda NG makes sense. However, if you want to create a report for the [[stable version]], you can '''manually''' download <tt>PDB</tt> files for this release.}}


=== Automatic method ===
=== Automatic method ===
If you have {{Plugin|en|PluginUpdater}} installed you can update your plugins and download debug symbols automatically.
If you have {{Plugin|en|PluginUpdater}} installed you can download the latest development version of plugins and the appropriate debug symbols automatically.
* Go to ''Options → Services → Plugin Updater → "Files source"''
* Go to ''Options → Services → Plugin Updater → "Files source"''
* Select ''Development version with debug symbols'' option and click ''OK''.
* Select ''Development version with debug symbols'' option and click ''OK''.
* Choose ''Check for plugin updates'' in the Main menu, click ''Update'' and wait till Miranda asks for restart.
* Choose ''Check for plugin updates'' from the Main menu, click ''Update'' and wait till Miranda asks for restart.


=== Manual method ===
=== Manual method ===
* Update manually '''all''' the plugins from the corresponding source (see [[Download]]).
* Using [[Download]] page update manually '''all''' the plugins and Miranda core files to the latest version:
* Download debug symbols archive <tt>miranda-ng-debug-symbols*.7z</tt> from the corresponding source ([http://miranda-ng.org/distr/stable/miranda-ng-debug-symbols_pdb.7z stable x32] [http://miranda-ng.org/distr/stable/miranda-ng-debug-symbols_pdb_x64.7z stable x64] / [http://miranda-ng.org/distr/miranda-ng-debug-symbols_pdb.7z latest x32] [http://miranda-ng.org/distr/miranda-ng-debug-symbols_pdb_x64.7z latest x64])
** Download the appropriate version of these plugins and core.
* Extract <tt>.pdb</tt> files named identically with your plugins from the archive to main Miranda NG folder. Do '''not''' extract anything to <tt>Plugins</tt> folder.
** Extract the contents of the archives into the main Miranda NG folder keeping the directory structure.
* From the [[Download#Core|Core]] section download debug symbols archive (<tt>miranda-ng-debug-symbols*.7z</tt>) of the same version as the plugins.
* Extract <tt>.pdb</tt> files named identically with your plugins from the archive to main Miranda NG folder. '''Do not extract anything to <tt>Plugins</tt> folder.'''
{{Message|message=Each time you update the plugins you have to re-download the debug symbols.}}




== Reproduce the crash ==
== Reproduce the crash ==
By default, crashlog files (<tt>.txt</tt> and <tt>.mdmp</tt>) are saved to <tt>Profiles\<Profile_name>\CrashLog\<Current_date></tt>.
Repeat the actions you performed before the crash occurred for the first time.
{{Message|message=Sometimes you may find that it is impossible to reproduce the crash. Perhaps the bug that caused it, was fixed in the current version.}}
If you succeeded and Miranda did crash again, check <tt>Profiles\<Profile_name>\CrashLog\<Current_date></tt> folder – crashlog files (<tt>.txt</tt> and <tt>.mdmp</tt>) are saved here by default.


; Examples
; Examples
Line 34: Line 40:
== Tips and tricks ==
== Tips and tricks ==
* Upload your crash reports to [http://pastebin.com pastebin.com] or [http://pastie.org pastie.org].
* Upload your crash reports to [http://pastebin.com pastebin.com] or [http://pastie.org pastie.org].
* Each time you update the plugins you have to re-download the debug symbols.





Revision as of 15:13, 29 July 2013

Template:Languages/Crash reports 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 CrashDumper

Install the appropriate version of CrashDumper plugin. You can do this manually (download links are found in the plugin card on its page) or automatically using PluginUpdater: go to Main Menu → Show full plugin list, select CrashDumper and click Download button.


Update plugins and debug symbols

All your plugins and Miranda core files must be of the latest version. Also, the debug symbols (PDB files) must be of the same compilation as the plugins, so it is necessary to update them too (or install if you don't have any).

All reported issues are checked and fixed on trunk, that's why creating crash reports using only the latest development version of Miranda NG makes sense. However, if you want to create a report for the stable version, you can manually download PDB files for this release.

Automatic method

If you have PluginUpdater installed you can download the latest development version of plugins and the appropriate debug symbols automatically.

  • Go to Options → Services → Plugin Updater → "Files source"
  • Select Development version with debug symbols option and click OK.
  • Choose Check for plugin updates from the Main menu, click Update and wait till Miranda asks for restart.

Manual method

  • Using Download page update manually all the plugins and Miranda core files to the latest version:
    •  Download the appropriate version of these plugins and core.
    •  Extract the contents of the archives into the main Miranda NG folder keeping the directory structure.
  • From the Core section download debug symbols archive (miranda-ng-debug-symbols*.7z) of the same version as the plugins.
  • Extract .pdb files named identically with your plugins from the archive to main Miranda NG folder. Do not extract anything to Plugins folder.
Each time you update the plugins you have to re-download the debug symbols.


Reproduce the crash

Repeat the actions you performed before the crash occurred for the first time.

Sometimes you may find that it is impossible to reproduce the crash. Perhaps the bug that caused it, was fixed in the current version.

If you succeeded and Miranda did crash again, check Profiles\<Profile_name>\CrashLog\<Current_date> folder – crashlog files (.txt and .mdmp) are saved here by default.

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


See also