Crash reports: Difference between revisions
(new PU feature "Dev version with debug symbols" described [en]) |
Dart Raiden (talk | contribs) No edit summary |
||
(30 intermediate revisions by 6 users not shown) | |||
Line 1: | Line 1: | ||
{{ | <languages/> | ||
Reports generated by {{Plugin | {{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>}} | ||
__TOC__ | |||
== Tips and tricks == | <translate> | ||
* | == Install CrashDumper == <!--T:2--> | ||
* | |||
<!--T:3--> | |||
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. | |||
== 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.</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: 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: 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}}}}]] |
Latest revision as of 16:59, 16 July 2022
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).
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.
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 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.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.
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
- Wrong: 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).
- Right: all debug symbols are in place, no lines "(filename not available) (0): (function-name not available)" with Miranda core/plugins names.
Tips and tricks
- Please use attachment system to add reports to our issue tracker (see How to attach files ). You can also upload reports to sites like pastebin.com, pastie.org and share a link.