##// END OF EJS Templates
Improve instructions on reporting crash...
Samuel Lelièvre -
Show More
@@ -45,10 +45,7 b' A crash report was automatically generated with the following information:'
45 45 It was left in the file named:
46 46 \t'{crash_report_fname}'
47 47 If you can email this file to the developers, the information in it will help
48 them in understanding and correcting the problem. Please include information
49 about your operating system: is it Linux, macOS, Windows, other, and which
50 version, for example Ubuntu 16.04, macOS 10.13.2, Windows 10 Pro 64-bit...
51 Please also include information on how you installed {app_name}.
48 them in understanding and correcting the problem.
52 49
53 50 You can mail it to: {contact_name} at {contact_email}
54 51 with the subject '{app_name} Crash Report'.
@@ -56,6 +53,16 b" with the subject '{app_name} Crash Report'."
56 53 If you want to do it now, the following command will work (under Unix):
57 54 mail -s '{app_name} Crash Report' {contact_email} < {crash_report_fname}
58 55
56 Please also include in your email:
57 - information about your operating system: is it Linux, macOS, Windows, other,
58 and which version, for example Ubuntu 16.04, macOS 10.13.2, Windows 10 Pro,
59 is it 32-bit or 64-bit, ...
60 - information on how you installed {app_name}: from binary, compiled from source,
61 via Docker, on a virtual machine...
62 - information on how to reproduce the crash: what exact sequence of instructions
63 can one input to get the same crash? Ideally, find a minimal yet complete
64 sequence of instructions that yields the crash.
65
59 66 To ensure accurate tracking of this issue, please file a report about it at:
60 67 {bug_tracker}
61 68 """
General Comments 0
You need to be logged in to leave comments. Login now