Crash reports: Difference between revisions

From Miranda NG
Jump to navigation Jump to search
(Новая страница: «{{Languages|ru=Создание краш-репортов|en=Crash reports|de=Crash Reports}} Reports generated by {{Plugin|CrashDumper}} by default are insuffic…»)
 
No edit summary
(37 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{{Languages|ru=Создание краш-репортов|en=Crash reports|de=Crash Reports}}
<languages/>
{{TNT|Important|<translate><!--T:1--> Reports generated by {{Plugin|CrashDumper}} by default are insufficient and of little use. To create a useful crash report you need to follow instructions provided below.</translate>}}


Reports generated by {{Plugin|CrashDumper}} by default are insufficient and of little use. To create a useful crash report you need to do the following:
__TOC__
* Install the {{Plugin|CrashDumper}} plugin (see the plugin card for download links)
* Update '''manually all''' the plugins from the corresponding source ([http://miranda-ng.org/distr/stable stable]/[http://miranda-ng.org/distr latest]). This is not the case to rely upon the {{Plugin|PluginUpdater}}.
* Download debug symbols archive <tt>miranda-ng-debug-symbols*.7z</tt> from the corresponding source (<tt>stable/latest</tt>, <tt>x32/x64</tt>)
* 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.
* Try to reproduce the crash.


; Examples
<translate>
# Wrong: [http://pastie.org/5456564 http://pastie.org/5456564]. Some debug symbols are missing which is denoted by lines "<tt>(filename not available) (0): (function-name not available)</tt>" with Miranda core/plugins names (Lines with <tt>USER32</tt>, <tt>ntdll</tt>, <tt>kernel32</tt>, etc. don't matter).
== Install CrashDumper == <!--T:2-->
# Right: [http://pastie.org/5456572 http://pastie.org/5456572]. All debug symbols are in place, no lines "<tt>(filename not available) (0): (function-name not available)</tt>" with Miranda core/plugins names.


== Tips and tricks ==
<!--T:3-->
* Upload your crash reports to [http://pastebin.com pastebin.com] or [http://pastie.org pastie.org].
Install the appropriate version of {{Plugin|CrashDumper}} plugin. You can do this manually (download links are found in the plugin card on its page) or automatically using {{Plugin|PluginUpdater}}: go to {{Menu|Main Menu|Available components list}}, select CrashDumper and click ''Download'' button.
* Each time you update the plugins you have to re-download the debug symbols.
 
== Update plugins and debug symbols == <!--T:4-->
 
<!--T:5-->
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).
</translate>
{{TNT|Important|<translate><!--T:6--> All reported issues are checked and fixed on trunk, that's why creating crash reports using only the latest {{GlossLink|development version}} of Miranda NG makes sense. However, if you want to create a report for the {{GlossLink|stable version}}, you can '''manually''' download PDB files for this release.</translate>}}
 
<translate>
=== Automatic method === <!--T:7-->
 
<!--T:8-->
If you have {{Plugin|PluginUpdater}} installed you can download the latest development version of plugins and the appropriate debug symbols automatically.
* Go to {{Menu|Options|Services|Plugin Updater|Files source}}
* Select ''Development version with debug symbols'' option and click ''OK''.
* Choose ''Check for updates'' from the Main menu, click ''Update'' and wait till Miranda asks for restart.
 
=== Manual method === <!--T:9-->
 
<!--T:10-->
* Using {{Ll|Download}} page update manually {{Strong|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 {{Ll|Download#Core|Core}} section download debug symbols archive (<tvar|archive_name>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. {{Strong|Do not extract anything to Plugins folder.}}</translate>{{TNT|Important|<translate><!--T:11--> Each time you update the plugins you have to re-download the debug symbols.</translate>}}
 
<translate>
 
== Reproduce the crash == <!--T:12-->
 
<!--T:13-->
Repeat the actions you performed before the crash occurred for the first time.
</translate>
{{TNT|Note|<translate><!--T:14--> Sometimes you may find that it is impossible to reproduce the crash. Perhaps the bug that caused it, was fixed in the latest version.</translate>}}
<translate>
<!--T:15-->
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.
 
== Example reports == <!--T:16-->
 
<!--T:17-->
# Wrong: [http://pastie.org/5456564 http://pastie.org/5456564]. Some debug symbols are missing which is denoted by lines "<tvar|report_entry>(filename not available) (0): (function-name not available)</>" with Miranda core/plugins names (Lines with <tvar|libs>USER32, ntdll, kernel32</>, etc. don't matter).
# Right: [http://pastie.org/5456572 http://pastie.org/5456572]. All debug symbols are in place, no lines "<tvar|report_entry>(filename not available) (0): (function-name not available)</>" with Miranda core/plugins names.
 
== Tips and tricks == <!--T:18-->
 
<!--T:19-->
* Please use attachment system to add reports to our issue tracker (see {{Ll|Reporting bugs#Effective bug reporting|How to attach files}}). You can also upload reports to sites like <tvar|pastebin_link>[https://pastebin.com pastebin.com]</>, <tvar|pastie_link>[http://pastie.org pastie.org]</> and share a link.
 
== See also == <!--T:20-->
</translate>
* {{Ll|Reporting bugs}}
 
[[Category:Help{{#translation:}}|{{#getdisplaytitle:{{FULLPAGENAME}}}}]]

Revision as of 21:00, 4 November 2018

Important
Reports generated by CrashDumper by default are insufficient and of little use. To create a useful crash report you need to follow instructions provided below.

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 → Available components 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).

Important
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 updates from the Main menu, click Update and wait till Miranda asks for restart.

Manual method

  • Using DownloadDownload 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 CoreDownload 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.
    Important
    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.

Note
Sometimes you may find that it is impossible to reproduce the crash. Perhaps the bug that caused it, was fixed in the latest 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.

Example reports

  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